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/jflamb/fdic-mcp-server/refactoringgit clone --depth 1 https://github.com/jflamb/fdic-mcp-serverWhat 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.00016 | $0.00188 |
| Opus 5 | $0.00008 | $0.00094 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
refactoring 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.
This is a copy
86% identical to refactoring — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/refactoring
Use this workflow when working on refactoring in fdic-mcp-server.
Goal
Code refactoring and cleanup workflow
Common Files
src/**/*
Suggested Sequence
- Understand the current state and failure mode before editing.
- Make the smallest coherent change that satisfies the workflow goal.
- Run the most relevant verification for touched files.
- Summarize what changed and what still needs review.
Typical Commit Signals
- Ensure tests pass before refactor
- Refactor code structure
- Verify tests still pass
Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.
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 · 35 lines · 16 tokens per session scan A 88a3f4c72662
refactoring is a command published in the GitHub repository jflamb/fdic-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 188 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to refactoring, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
implement
yes, thank you! please proceed with implementation.
create-forwarding-rule
Create a ZPA client forwarding policy rule to bypass or intercept traffic.
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.
spec-plan
Run a resumable spec interview to produce spec.json/spec.md (planning-time), then optionally compile to prd.json. Usage: /plan-cascade:spec-plan " " [--output-dir ] [--flow ] [--first-principles] [--max-questions N] [--feature-slug ] [--compile] [--tdd ] [--confirm] [--no-confirm].
adops-audit
Multi-dimensional GAM audit: delivery health, inventory hygiene, security baseline, creative compliance, billing alignment. Read-only and free.
audit
Audit installed agents/skills - find never-used or stale ones and help prune them.