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.
git clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/policyengine/policyengine-claude/setup-verbs)<a href="https://agentmods.dev/commands/policyengine/policyengine-claude/setup-verbs"><img src="https://agentmods.dev/badge/commands/policyengine/policyengine-claude/setup-verbs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/policyengine/policyengine-claude/setup-verbs"><img src="https://agentmods.dev/badge/commands/policyengine/policyengine-claude/setup-verbs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00011 | $0.00447 |
| Opus 5.5 | $0.00004 | $0.00179 |
| Sonnet 5.5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade B, and why
setup-verbs scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Install PolicyEngine-themed spinner verbs (the loading messages that appear while Claude is thinking) into the user's `~/.claude/settings.json`. What it actually says
Install PolicyEngine spinner verbs
Install PolicyEngine-themed spinner verbs (the loading messages that appear while Claude is thinking) into the user's ~/.claude/settings.json.
Steps
- Read the user's current
~/.claude/settings.json - Check if
spinnerVerbsis already configured - If already configured, show the user what's there and ask if they want to replace it
- If not configured (or user confirms replacement), merge the following
spinnerVerbsblock into their settings JSON, preserving all other existing settings:
"spinnerVerbs": {
"mode": "replace",
"verbs": [
"Microsimulating",
"Means-testing",
"Phasing out benefits",
"Calculating MTRs",
"Clawing back subsidies",
"Navigating the subsidy cliff",
"Modeling counterfactuals",
"Imputing income",
"Reweighting the CPS",
"Parsing the CFR",
"Adjudicating eligibility",
"Benchmarking silver plans",
"Risk-adjusting",
"Sunsetting provisions",
"Scoring the bill",
"Applying the benefit reduction rate",
"Overfitting",
"Simulating takeup",
"Inflation adjusting",
"Ignoring behavioral responses",
"Querying HMRC",
"Means-testing the telly licence",
"Freezing the thresholds",
"Preserving the triple lock",
"Scoring the autumn budget",
"Estimating impacts",
"Building the baseline",
"Reforming the tax code",
"Calculating taxes",
"Simulating policy",
"Crunching the numbers"
]
}
- Write the updated JSON back to
~/.claude/settings.jsonwith proper formatting (2-space indent) - Tell the user the verbs are installed and they'll see them next time Claude is thinking
IMPORTANT: Preserve all existing settings (permissions, hooks, enabledPlugins, etc.). Only add or replace the spinnerVerbs key.
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.
- 1mo ago First seen · 59 lines · 11 tokens per session scan B ea5b824171d4
setup-verbs is a command published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 447 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.