Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bromso/metapowers/plugin install 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/skills/bromso/metapowers/scenario)<a href="https://agentmods.dev/skills/bromso/metapowers/scenario"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/scenario/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/scenario"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/scenario.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.00066 | $0.00740 |
| Opus 5.5 | $0.00026 | $0.00296 |
| Sonnet 5.5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
scenario 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario
Model financial scenarios for "$ARGUMENTS". Build structured best/base/worst-case projections to understand the range of possible outcomes and prepare contingency plans.
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
None — utility skill, run anytime. Works best when financial data exists in .metapowers/finance/<project>/.
Process
-
Gather context:
- If prior phase artifacts exist, read them for baseline data
- Ask the user what decision or question the scenarios should inform
- Determine the time horizon for the scenarios
-
Define scenario parameters:
- Identify the 5-8 key variables that drive outcomes (revenue growth, churn, ARPU, hiring pace, etc.)
- For each variable, define best/base/worst values with rationale
- Reference
${CLAUDE_PLUGIN_ROOT}/shared/financial-model-template.mdfor scenario table structure
-
Build three scenarios:
- Best case: optimistic but plausible assumptions
- Base case: most likely outcome based on current trajectory
- Worst case: pessimistic but survivable assumptions
- For each: project revenue, expenses, cash flow, and runway
-
Analyze implications:
- What decisions change between scenarios?
- At what point does the worst case become dangerous?
- What early warning signals distinguish which scenario is unfolding?
- What contingency actions should be prepared?
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 · 60 lines · 66 tokens per session scan A 3259d77620c7
scenario is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 740 once invoked, about $0.0003 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
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
mergers-and-acquisitions
Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business…
financial-modeling
Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or…
tax
Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…
treasury-and-liquidity
Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.
payroll-operations
Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and the deductions in it, multi-jurisdiction registration and tax filing, off-cycle payments and corrections, and the reconciliation to the general ledger. Use this to design…