Menu
Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Invoke and resume YAML-defined pipelines by name — /pipeline auto-dev runs the full release pipeline
Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
On explicit /homework invocation, analyze the current and linked previous sessions, extract mistakes (찐빠), and report them via omcustom-feedback with a confirmation gate. Auto-activation on session cleanup/session-end signals is OPT-IN (default OFF) — requires an explicit project/user directive. Use when explicitly auditing recent work for harness gaps.
hada.io RSS feed monitoring for AI agent/harness articles with automated /scout analysis
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation
| name | action-validator |
| description | Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts |
| scope | core |
| user-invocable | false |
Advisory pre-action validation layer that checks agent tool calls against declared capabilities, file access scope (R002), and task contracts before execution. Inspired by AutoHarness (Google DeepMind) — enforcing action-space legality at agent boundaries.
This skill does NOT block actions (R021 advisory-first model). It emits warnings when agents attempt operations outside their declared scope.
| Check | What | Against |
|---|---|---|
| Tool scope | Tool being called | Agent's tools frontmatter list |
| File scope | File path in Write/Edit | R002 file access rules |
| Domain scope | Target file extension | Agent's domain frontmatter |
| Task contract | Operation type | Task description constraints |
--- [Action Validator] Scope warning ---
Agent: {agent-name}
Tool: {tool-name}
Target: {file-path}
Issue: {description}
Declared scope: {agent's declared tools/domain}
💡 Suggestion: {recommended action}
---
| System | How |
|---|---|
| PreToolUse hooks | Optional hook to check tool calls (advisory only) |
| pipeline-guards | Complements pipeline stage gates |
| adversarial-review | Provides action-space-legality criterion |
| R002 (Permissions) | Validates against declared file access rules |
| R010 (Orchestrator) | Orchestrator validates subagent scope claims |
For high-repetition agents (e.g., mgr-gitnerd commit workflows), capture validated decision paths as reusable policies:
policy_cache:
agent: mgr-gitnerd
action: git-commit
validated_steps:
- tool: Bash
pattern: "git add *"
verdict: allow
- tool: Bash
pattern: "git commit *"
verdict: allow
- tool: Bash
pattern: "git push *"
verdict: warn_confirm
Policy caching reduces redundant LLM calls for well-understood workflows. Policies are advisory — the orchestrator may override.
This skill is an advisory layer, not a hard enforcement mechanism: