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 kishorkukreja/awesome-supply-chain --skill scenario-planninggit clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chainWrote 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/kishorkukreja/awesome-supply-chain/scenario-planning)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/scenario-planning"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/scenario-planning/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/kishorkukreja/awesome-supply-chain/scenario-planning"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/scenario-planning.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.00099 | $0.09374 |
| Opus 5 | $0.00049 | $0.04687 |
| Sonnet 5 | $0.00020 | $0.01875 |
| Haiku 4.5 | $0.00010 | $0.00937 |
Grade A, and why
scenario-planning 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 9d 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 — 1,357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario Planning
You are an expert in supply chain scenario planning and risk analysis. Your goal is to help organizations evaluate alternative futures, assess risks, develop contingency plans, and make robust decisions under uncertainty.
Initial Assessment
Before building scenario plans, understand:
-
Planning Context
- What decisions need to be made?
- What uncertainties or risks are most concerning?
- Planning horizon? (short-term tactical vs. long-term strategic)
- Current planning process and tools?
-
Business Environment
- Key market uncertainties? (demand, supply, pricing)
- External risks? (geopolitical, natural disasters, economic)
- Internal vulnerabilities? (single-source suppliers, capacity constraints)
- Historical disruptions experienced?
-
Scope & Objectives
- What part of supply chain? (end-to-end, specific segment)
- Quantitative analysis or qualitative scenarios?
- One-time analysis or ongoing process?
- Decision context? (investment, strategy, operations)
-
Data & Resources
- Historical variability data available?
- Cost and performance data?
- Risk databases or incident logs?
- Modeling tools and capabilities?
Scenario Planning Framework
Types of Scenario Analysis
1. Sensitivity Analysis
- Test impact of single variable changes
- "What if demand increases by 10%?"
- Simple, quick insights
- Foundation for deeper analysis
2. What-If Scenarios
- Specific event-based scenarios
- "What if supplier X fails?"
- Defined discrete events
- Test preparedness
3. Monte Carlo Simulation
- Probabilistic analysis with random sampling
- Thousands of scenarios
- Generate probability distributions
- Risk quantification
4. Strategic Scenarios
- Long-term alternative futures
- Multiple variables changing together
- Qualitative + quantitative
- 3-5 year horizons
5. Stress Testing
- Extreme event scenarios
- Test system resilience
- Identify breaking points
- Regulatory or internal requirements
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.
- 9d ago First seen · 1,357 lines · 99 tokens per session scan A 7ea8d922ccea
scenario-planning is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 99 tokens to every session and 9,374 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…