Borrowing it
Nothing to install: this file belongs to jflamb/fdic-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jflamb/fdic-mcp-server/main/.claude/commands/fdic-examiner-overlay.mdgit clone --depth 1 https://github.com/jflamb/fdic-mcp-serverWrote 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/jflamb/fdic-mcp-server/fdic-examiner-overlay)<a href="https://agentmods.dev/commands/jflamb/fdic-mcp-server/fdic-examiner-overlay"><img src="https://agentmods.dev/badge/commands/jflamb/fdic-mcp-server/fdic-examiner-overlay.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.1 | $0.00060 | $0.09181 |
| Opus 5 | $0.00030 | $0.04591 |
| Sonnet 5 | $0.00012 | $0.01836 |
| Haiku 4.5 | $0.00006 | $0.00918 |
Grade A, and why
fdic-examiner-overlay 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 756 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fdic-examiner-overlay
Skill Type: RIGID
This workflow is non-negotiable in structure. You MUST follow every step in order. You MUST NOT skip the confirmation gate. You MUST NOT merge provenance layers in the narrative.
Every paragraph or finding in the final output must be attributed to its source layer:
- Public data indicate... — proxy baseline findings
- Examiner overlay: — analyst-provided inputs
- Blended interpretation: — combined assessment
These three layers must NEVER be merged into undifferentiated prose.
Step 1: Fetch Baseline
Ask the analyst:
"Which institution would you like to assess? Provide the CERT number, and optionally a report date (YYYYMMDD)."
Once you have the CERT (and optional repdte):
- Call the
fdic_analyze_bank_healthMCP tool with the providedcertandrepdte(or omit repdte for the default latest quarter). - From the tool result, extract:
structuredContent.proxy— the fullProxyAssessmentobject (quantitative baseline)structuredContent.institution— identity fields (name, city, state, charter_class, total_assets, report_date, data_staleness)structuredContent.risk_signals— legacy risk signal listcontent[0].text— the human-readable text summary (for reference)
- Store these as the baseline for the remainder of the workflow.
If the tool call fails or returns no data, report the error and stop. Do not proceed without a valid baseline.
Step 2: Present Baseline Summary
Present the baseline to the analyst in this exact format:
Public Data Baseline
Institution: [name] (CERT [cert]), [city], [state] Report Date: [repdte] | Data Staleness: [staleness]
Overall: [band] ([score]/4.0)
| Component | Score | Label | Key Flag |
|---|---|---|---|
| Capital | [score] | [label] | PCA: [category] |
| Asset Quality | [score] | [label] | |
| Earnings | [score] | [label] | |
| Liquidity/Funding | [score] | [label] | |
| Sensitivity Proxy | [score] | [label] |
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.
- 7d ago First seen · 756 lines · 60 tokens per session scan A c28047ae0efb
fdic-examiner-overlay is a command published in the GitHub repository jflamb/fdic-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 9,181 once invoked, about $0.0003 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.
search-flights
Search award flight availability across airlines.
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.