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 scenariogit 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)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/scenario"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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/davidroliverba/architectkb/scenario"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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.00000 | $0.01644 |
| Opus 5 | $0.00000 | $0.00822 |
| Sonnet 5 | $0.00000 | $0.00329 |
| Haiku 4.5 | $0.00000 | $0.00164 |
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 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scenario
Create a Scenario note for what-if analysis, future-state planning, alternative architecture options, or risk mitigation strategies.
Usage
/scenario <name>
/scenario "SAP Cloud Migration"
/scenario "Real-time Analytics" --type future-state
/scenario "Vendor Alternative: Google vs AWS" --type alternative-option
Instructions
Phase 1: Parse Input & Type
- Extract scenario name
- Ask for scenario type:
Scenario Type: - current-state (baseline for comparison) - future-state (where we want to go) - alternative-option (different approach) - risk-mitigation (contingency plan) Default: future-state
Phase 2: Baseline Architecture
What is the baseline architecture for this scenario?
(Choose existing Architecture note)
Search: [[Architecture - Current State HLD]]
Found: [[Architecture - Current State HLD]]
Confirm baseline? (Y/n)
> y
Phase 3: What Changes?
For future-state / alternative scenarios, ask:
What changes from the baseline?
System Additions (comma-separated or one per line):
> SAP S/4HANA Cloud
> SAP Event Mesh
System Removals:
> SAP LegacyEngineeringSystem (legacy)
System Modifications:
> DataPlatform (add real-time event consumer)
> Snowflake (increase storage)
Integration Changes:
> Add: Event-driven SAP to DataPlatform
> Remove: Daily batch sync
> Modify: DataPlatform to Snowflake (add real-time)
Phase 4: Systems Involved
Systems in this scenario (for quick view):
- [[System - SAP S/4HANA Cloud]]
- [[System - Event Mesh]]
- [[System - DataPlatform]]
- [[System - Snowflake]]
Phase 5: Impact Analysis
Ask: "Analyse impact? (Y/n)"
If YES:
BUSINESS IMPACT:
Benefits:
> Real-time data enables faster decisions
> Reduced reporting lag from 24h to <1s
> Better customer experience
Risks:
> Migration disruption (1-2 week freeze)
> Higher licensing costs
> Team learning curve
TECHNICAL IMPACT:
Capabilities enabled:
> Event-driven architecture
> Real-time data pipelines
> Stream processing
Technical debt reduced:
> Legacy LegacyEngineeringSystem system (EOL'd)
> Point-to-point integrations (replaced)
> Batch workflows (replaced with streams)
COST IMPACT:
Implementation: £1,250,000
- SAP migration: £800k
- Integration: £300k
- Analytics: £150k
Annual savings: £250,000 (infrastructure reduction)
Payback: 5 years
ORGANIZATIONAL IMPACT:
Resources: 27 people over 12 months
Budget: £1,250,000
Skills needed: SAP Cloud, Event-driven patterns, Kafka
Training required: 2 weeks per person
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 · 307 lines · 0 tokens per session scan A b954dd79e5a0
scenario 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 1,644 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…