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 travisjneuman/.claude --skill financial-scenario-plannergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/financial-scenario-planner)<a href="https://agentmods.dev/skills/travisjneuman/.claude/financial-scenario-planner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/financial-scenario-planner/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/travisjneuman/.claude/financial-scenario-planner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/financial-scenario-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.02927 |
| Opus 5.5 | $0.00018 | $0.01171 |
| Sonnet 5.5 | $0.00009 | $0.00585 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade A, and why
financial-scenario-planner 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 1mo 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Scenario Planner
Frameworks for building multi-scenario financial models, stress testing assumptions, sensitivity analysis, and probability-weighted financial planning.
Scenario Analysis Framework
Three-Scenario Model
SCENARIO PLANNING TEMPLATE:
BEAR CASE BASE CASE BULL CASE
(Pessimistic) (Expected) (Optimistic)
Probability: 20-25% 50-60% 20-25%
REVENUE ASSUMPTIONS:
Growth rate: [X%] [X%] [X%]
New customers: [N] [N] [N]
Churn rate: [X%] [X%] [X%]
ARPU change: [X%] [X%] [X%]
Market size: [$ ] [$ ] [$ ]
COST ASSUMPTIONS:
COGS margin: [X%] [X%] [X%]
Headcount growth: [N] [N] [N]
Salary inflation: [X%] [X%] [X%]
Marketing spend: [$ ] [$ ] [$ ]
Capex: [$ ] [$ ] [$ ]
EXTERNAL FACTORS:
Interest rates: [X%] [X%] [X%]
Inflation: [X%] [X%] [X%]
FX rates: [X ] [X ] [X ]
Regulatory: [Impact] [Impact] [Impact]
PROJECTED OUTCOMES:
Revenue: [$ ] [$ ] [$ ]
EBITDA: [$ ] [$ ] [$ ]
Net income: [$ ] [$ ] [$ ]
Cash position: [$ ] [$ ] [$ ]
Runway (months): [N] [N] [N]
EXPECTED VALUE:
E[Revenue] = P(bear) x Rev(bear) + P(base) x Rev(base) + P(bull) x Rev(bull)
Scenario Trigger Events
| Scenario Driver | Bear Trigger | Base Assumption | Bull Trigger |
|---|---|---|---|
| Market demand | Recession, -15% | Steady growth, +5% | Market expansion, +20% |
| Competition | New entrant takes 20% share | Stable competition | Competitor exits market |
| Regulation | Restrictive new regulation | Status quo | Deregulation/favorable policy |
| Technology | Disruption makes product obsolete | Incremental improvement | Breakthrough advantage |
| Funding | Cannot raise next round | Raise at expected terms | Oversubscribed round |
| Key personnel | Lose critical team members | Normal retention | Key strategic hires |
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.
- 1mo ago First seen · 340 lines · 44 tokens per session scan A 6cd075ec4f74
financial-scenario-planner is a skill published in the GitHub repository travisjneuman/.claude (106 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,927 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…