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/datarails/dr-claude-code-plugins-re/budget-comparisongit clone --depth 1 https://github.com/Datarails/dr-claude-code-plugins-reWrote 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/datarails/dr-claude-code-plugins-re/budget-comparison)<a href="https://agentmods.dev/commands/datarails/dr-claude-code-plugins-re/budget-comparison"><img src="https://agentmods.dev/badge/commands/datarails/dr-claude-code-plugins-re/budget-comparison.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.00017 | $0.00205 |
| Opus 5 | $0.00009 | $0.00102 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
budget-comparison 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.
What it actually says
Budget vs Actual Comparison
This command is a thin launcher — the single maintained recipe for plan-vs-actual
analysis lives in the datarails-financeos:forecast-variance skill. Do not improvise workflow
steps here.
Invoke the datarails-financeos:forecast-variance skill with the user's request framed as a
budget-vs-actual comparison, passing through any period (--year), scenario, or
category focus they named.
Notes for the handoff:
- The skill discovers the scenario domain at runtime. If no budget-like scenario exists (common — many orgs carry only actuals/forecast scenarios), it uses the discovered planning-version-like field as the plan side, and degrades gracefully to comparing the scenarios that do exist.
- All variance math is period-scoped and labeled with period + scenario.
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 · 22 lines · 17 tokens per session scan A 41e7fcdef089
budget-comparison is a command published in the GitHub repository Datarails/dr-claude-code-plugins-re (3 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 205 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
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
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.
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…