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 skills add bromso/metapowers --skill budgetgit clone --depth 1 https://github.com/bromso/metapowersWrote 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/skills/bromso/metapowers/budget)<a href="https://agentmods.dev/skills/bromso/metapowers/budget"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/budget/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bromso/metapowers/budget"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/budget.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.00793 |
| Opus 5.5 | $0.00019 | $0.00317 |
| Sonnet 5.5 | $0.00010 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
budget 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Budget
Allocate the budget for "$ARGUMENTS". Break down the forecast into departmental budgets with spending limits, approval thresholds, and accountability.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/finance/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Compute with code. Perform every calculation (totals, balances, ratios, variances, projections) with a script — Bash, Python or a spreadsheet formula written to a file — and include the computation alongside the result. Never do arithmetic mentally.
Prerequisites
Read .metapowers/finance/<project>/03-forecast.md. If this file does not exist, tell the user:
Phase 3 (Forecast) has not been completed for "". Run
/finance:forecast <project>first, or use--skip-checksto bypass.
Process
-
Read context:
- Read
.metapowers/finance/<project>/02-plan.mdfor strategic objectives - Read
.metapowers/finance/<project>/03-forecast.mdfor expense projections
- Read
-
Define budget structure:
- List all departments or cost centers
- Categorize expenses: personnel, tools/software, marketing, infrastructure, professional services, other
- Determine budget period (monthly, quarterly, annual)
-
Allocate by department:
- For each department:
- Personnel costs (headcount x compensation)
- Non-personnel costs (tools, travel, contractors, etc.)
- Growth investments vs maintenance spend
- Ensure allocations sum to the forecast total
- Identify which departments have the most budget flexibility
- For each department:
-
Set guardrails:
- Define spending authority levels (who can approve what amounts)
- Set variance thresholds that trigger review (e.g., >10% over budget)
- Identify protected vs discretionary line items
- Define the reallocation process
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 · 69 lines · 48 tokens per session scan A b8b72c87652e
budget is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 793 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
lead-orchestration
Use when you are the LEAD (main session) and an owner request arrives that needs agents -- intake, routing, briefs, follow-up, blocks, verification, learning, report. Canonical procedure from request to verified report; not for sub-agents executing a brief.
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
incident-management
Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes.…