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/feature-developmentgit 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.00203 |
| Opus 5 | $0.00008 | $0.00102 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
feature-development 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 yesterday.
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
/feature-development
Use this workflow when working on feature-development in fdic-mcp-server.
Goal
Standard feature implementation workflow
Common Files
src/schemas/*src/tools/*src/tools/shared/***/*.test.*
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
- Add feature implementation
- Add tests for feature
- Update documentation
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.
- yesterday First seen · 38 lines · 16 tokens per session scan A a20315fcffe7
feature-development 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 203 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 commands, from other repositories
research
Professional equity research analysis with institutional-grade formatting.
log-incident
Capture a new entry in INCIDENTS.md from the latest workspace run. Human-gated curation step of the Anamnesis Pattern's Curate beat. Drafts a candidate entry; the user confirms before append.
monitor
Position monitoring — watchlist, thesis check, event radar, thesis tracker, catalyst calendar, morning note.
macro
Macro & economic research — yield curve, trade flows, labor market.
commit
This command helps you create well-formatted commits with conventional commit messages and emoji.
code-review
Code review a pull request.