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/bankstatemently/plugins/reconcilegit clone --depth 1 https://github.com/bankstatemently/pluginsWhat 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.00041 | $0.00305 |
| Opus 5 | $0.00020 | $0.00152 |
| Sonnet 5 | $0.00008 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
reconcile 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
Input: $ARGUMENTS
Reconcile
Input: the account, product, date range, or free-text scope to reconcile. Output: a concise reconciliation report with covered periods, missing periods, balance-continuity breaks (with source content_hash pairs), and transfer findings.
Treat the input as the account, product, date range, or free-text scope to reconcile.
Follow this sequence:
- Call
list_statementsto find statements in scope. - For each completed statement in scope, call
get_statement. - Sort statements by account and period. Report missing periods, overlapping periods, and gaps.
- Compare each closing balance with the next opening balance for the same account. Report every balance-continuity break with the two source content_hash values.
- Call
list_transfersfor the same scope to identify cross-account matches and large unmatched movements when relevant. - Present a concise reconciliation report with the account scope, covered periods, missing periods, balance-continuity breaks, and transfer findings.
Example prompt: Reconcile my savings account for 2024 — flag missing months and any balance breaks.
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 · 28 lines · 41 tokens per session scan A 61ae2c4d3d06
reconcile is a command published in the GitHub repository bankstatemently/plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 305 once invoked, about $0.0002 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
make
Create structured implementation plan in docs/plans/.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.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.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.