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/brainbytes-dev/everything-claude-finance/budget-forecastgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-financeWrote 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/brainbytes-dev/everything-claude-finance/budget-forecast)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-finance/budget-forecast"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-finance/budget-forecast.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.00009 | $0.01266 |
| Opus 5 | $0.00005 | $0.00633 |
| Sonnet 5 | $0.00002 | $0.00253 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
budget-forecast 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/budget-forecast — Budget and Forecast
What This Command Does
Creates structured budget plans and rolling forecasts with clear assumption documentation, departmental breakdowns, and variance tracking frameworks. Supports annual budgets, quarterly reforecasts, rolling 12-month forecasts, and zero-based budgeting approaches.
When to Use
- Annual budget cycle preparation
- Quarterly reforecast updates
- New business unit budget creation
- Zero-based budgeting exercises
- Board-ready budget presentations
- Cash flow forecasting for treasury
How It Works
- Revenue Planning: Top-down and bottom-up revenue build with segment detail
- Cost Budgeting: Fixed vs. variable cost separation, headcount planning, discretionary spend allocation
- Capital Budget: Capex planning with project-level detail and ROI thresholds
- Working Capital: Cash conversion cycle assumptions and seasonal patterns
- Consolidation: Roll-up across departments/entities with elimination entries
- Variance Framework: Sets up tracking structure for actual-vs-budget monitoring
Example Usage
Input:
/budget-forecast entity:"Marketing Department" type:annual period:FY2026 currency:USD
Output:
# Marketing Department — Annual Budget FY2026
## Entity: Global Marketing | Currency: USD thousands | Approved: Draft
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Budget Summary
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Category | FY2025A | FY2026B | Δ % | Commentary |
|--------------------|---------|---------|--------|------------------------------|
| Headcount (FTEs) | 24 | 28 | +16.7% | 4 new hires (2 digital, 2 content) |
| Personnel costs | 2,880 | 3,500 | +21.5% | Includes new hires + 4% raises |
| Program spend | 1,800 | 2,100 | +16.7% | Shift to digital channels |
| Technology/tools | 350 | 420 | +20.0% | New marketing automation |
| Travel & events | 200 | 250 | +25.0% | 2 additional trade shows |
| **Total Budget** | **5,230** | **6,270** | **+19.9%** | |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Monthly Phasing
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| USD '000 | Jan | Feb | Mar | Q1 | Apr | May | Jun | Q2 | H1 |
|----------|-----|-----|-----|------|-----|-----|-----|------|-------|
| Personnel| 280 | 280 | 280 | 840 | 292 | 292 | 292 | 876 | 1,716 |
| Programs | 120 | 150 | 200 | 470 | 175 | 175 | 225 | 575 | 1,045 |
| Tech | 35 | 35 | 35 | 105 | 35 | 35 | 35 | 105 | 210 |
| Travel | 10 | 15 | 30 | 55 | 20 | 25 | 20 | 65 | 120 |
| **Total**| 445 | 480 | 545 |1,470 | 522 | 527 | 572 |1,621 | 3,091 |
[Assumption: New hires start April 1 — personnel ramps in Q2]
[Assumption: Trade show spend concentrated in Mar and Sep]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## KPI Targets
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| KPI | FY2025A | FY2026B | Target Basis |
|------------------------|---------|---------|-------------------------|
| CAC (Customer Acq.) | $285 | $250 | Improve with automation |
| Marketing % of revenue | 8.2% | 7.8% | Scale leverage |
| MQL to SQL conversion | 18% | 22% | Better targeting |
| Pipeline contribution | $32M | $42M | +31% aligned to rev plan |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Variance Tracking Template
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Category | Budget | Actual | Variance | Var % | Explanation |
|-------------|--------|--------|----------|-------|-------------|
| Personnel | — | — | — | — | |
| Programs | — | — | — | — | |
| Technology | — | — | — | — | |
| Travel | — | — | — | — | |
| **Total** | — | — | — | — | |
Threshold: Variances > 5% require written explanation.
Threshold: Variances > 10% require VP approval for corrective action.
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.
- 4d ago First seen · 115 lines · 9 tokens per session scan A 026445ec95ea
budget-forecast is a command published in the GitHub repository brainbytes-dev/everything-claude-finance (5 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 1,266 once invoked, about $0.0000 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
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
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…
archive-ledger
../../../shared/commands/archive-ledger.md.