Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/agentic-swe/agentic-swe/policygit clone --depth 1 https://github.com/agentic-swe/agentic-sweWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00299 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
policy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/policy
Inspect and explain the active Policy-as-Code configuration.
Subcommands
/policy show
Display the effective merged policy (pack default + repo .agentic-swe/policy.json + org AGENTIC_SWE_POLICY).
/policy explain <state>
Show what the policy enforces for a specific pipeline state:
- Minimum track (from
track_rulesmatching the current diff) - Mandatory subagents (from
mandatory_subagentsmatching touched files) - Banned tools
- Additional required artifacts
- Budget overrides
/policy check
Validate the repo's .agentic-swe/policy.json against ${CLAUDE_PLUGIN_ROOT}/schemas/agentic-swe-policy.schema.json. Report errors if the policy is malformed.
Behavior
- Resolve the effective policy via
${CLAUDE_PLUGIN_ROOT}/scripts/lib/policy/merge.cjs. - For
show: pretty-print the merged result. - For
explain <state>: filter rules relevant to the given state and current diff. - For
check: validate schema and report.
Integration
The policy is evaluated during:
lean-track-check—track_rulesmay force a minimum track- Phase delegation —
mandatory_subagentsare enforced - Tool invocations —
banned_toolsare checked pre-execution - Artifact validation —
required_artifactsare merged with pack defaults
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 38 lines · 0 tokens per session scan A 635fb90d2233
policy is a command published in the GitHub repository agentic-swe/agentic-swe (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 299 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.