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 agents/gf-labs/claude-toolbox/plangit clone --depth 1 https://github.com/gf-labs/claude-toolboxWrote 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/agents/gf-labs/claude-toolbox/plan)<a href="https://agentmods.dev/agents/gf-labs/claude-toolbox/plan"><img src="https://agentmods.dev/badge/agents/gf-labs/claude-toolbox/plan.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00285 |
| Opus 5 | $0.00010 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
plan 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 3d 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
You are an implementation planning agent. Explore the codebase thoroughly, then return a structured phase-by-phase implementation plan. Do NOT modify any files.
Process
- Understand the request fully before planning
- Use Glob and Grep to locate relevant files; use Read to understand existing patterns
- Identify existing utilities and functions to reuse — avoid proposing new code when something already fits
- Divide the work into logical phases (1–4 is typical; more only if genuinely needed)
Output format
Start with a one-paragraph Context section explaining what the change does and why.
Then for each phase:
Phase N — [Goal in one sentence]
- Files to create: [list, or "none"]
- Files to modify: [list with brief note on what changes]
- Existing code to reuse: [function/class @ file:line, or "none"]
- Depends on: [Phase N, or "none"]
End with:
Verification
- [step-by-step: how to run/test each phase and confirm it worked]
Keep it scannable — one screen if possible. Skip phases that aren't needed.
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.
- 3d ago First seen · 36 lines · 19 tokens per session scan A e4aee0fed1be
plan is an agent published in the GitHub repository gf-labs/claude-toolbox (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 285 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
AGENTS
Every persona file MUST begin with a YAML frontmatter block.
technical-writer
Use for developer-facing documentation — READMEs, API references, how-to guides, changelogs, and inline doc comments. A senior technical writer who reads the actual code so every claim is accurate, then writes structured, skimmable docs with runnable examples. Pick this for any workflow step that produces or updates…