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/fergupa/claude_plugins/reconciliationgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/reconciliation)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/reconciliation"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/reconciliation.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.00014 | $0.01261 |
| Opus 5 | $0.00007 | $0.00630 |
| Sonnet 5 | $0.00003 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
reconciliation 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Account Reconciliation
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Important: This command assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off.
Reconcile GL account balances to subledger, bank, or third-party balances. Identify and categorize reconciling items and generate a reconciliation workpaper.
Usage
/recon <account> <period>
Arguments
account— The account or account category to reconcile. Examples:cashorbank— Bank reconciliation (GL cash to bank statement)accounts-receivableorar— AR subledger reconciliationaccounts-payableorap— AP subledger reconciliationfixed-assetsorfa— Fixed asset subledger reconciliationintercompanyoric— Intercompany balance reconciliationprepaid— Prepaid expense schedule reconciliationaccrued-liabilities— Accrued liabilities detail reconciliation- Any specific GL account code (e.g.,
1010,2100)
period— The accounting period end date (e.g.,2024-12,2024-12-31)
Workflow
1. Gather Both Sides of the Reconciliation
If ~~erp or ~~data warehouse is connected:
- Pull the GL balance for the specified account(s) as of period end
- Pull the subledger, bank statement, or third-party balance for comparison
- Pull prior period reconciliation (if available) for outstanding item carryforward
If no data source is connected:
Connect ~~erp or ~~data warehouse to pull account balances automatically. To reconcile manually, provide:
- GL side: The general ledger balance for the account as of period end
- Other side: The subledger balance, bank statement balance, or third-party confirmation balance
- Prior period outstanding items (optional): Any reconciling items from the prior period reconciliation
2. Compare Balances
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 · 148 lines · 14 tokens per session scan A 5805489942dd
reconciliation is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,261 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
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…