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 DavidROliverBA/ArchitectKB --skill scenario-comparegit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/scenario-compare)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/scenario-compare"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/scenario-compare/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/davidroliverba/architectkb/scenario-compare"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/scenario-compare.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.00000 | $0.03130 |
| Opus 5 | $0.00000 | $0.01565 |
| Sonnet 5 | $0.00000 | $0.00626 |
| Haiku 4.5 | $0.00000 | $0.00313 |
Grade A, and why
scenario-compare 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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scenario-compare Skill
Compare multiple scenarios with cost, timeline, complexity, and impact analysis.
When to Use This Skill
Use /scenario-compare when you need to evaluate and compare different architectural options:
- Compare baseline vs proposed scenarios
- Evaluate alternatives (e.g., AWS vs Snowflake BI tool options)
- Create decision matrices for technology choices
- Generate business case analysis
- Create executive briefings comparing options
Usage
/scenario-compare <primary-scenario> [comparisons] [options]
Parameters
| Parameter | Description | Required |
|---|---|---|
primary-scenario |
Base scenario to compare against | Yes |
comparisons |
Comma-separated list of comparison scenarios | Yes (≥1) |
--metrics |
Which metrics to compare (cost, timeline, complexity, impact, risk) | Optional |
--stakeholder |
Audience (executive, technical, financial) | Optional |
--horizon |
Time horizon (1yr, 3yr, 5yr) | Optional |
--format |
Output format (markdown, spreadsheet, presentation) | Optional |
Workflow
Phase 1: Define Scenarios
User specifies:
-
Primary scenario (baseline)
- Can be "current-state" or existing Scenario note
- Example: [[Scenario - Real-time Analytics Expansion]]
-
Comparison scenarios (alternatives)
- Comma-separated: "Alternative 1, Alternative 2, Alternative 3"
- Can be existing notes or user-described scenarios
- Typically 2-3 alternatives for comparison
-
What to compare (optional)
- Default: All metrics (cost, timeline, complexity, impact, risk)
- Options:
cost- Setup and ongoing coststimeline- Implementation duration and phasescomplexity- Technical and operational difficultyimpact- Business benefit and riskrisk- Technical, organizational, financial risksvendor- Vendor lock-in and independencescalability- Growth potential
Phase 2: Extract Data
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 · 481 lines · 0 tokens per session scan A 2a7296f21f90
scenario-compare is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,130 tokens. 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…