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 agentmods add skills/davidroliverba/architectkb/impact-analysisnpx skills add DavidROliverBA/ArchitectKB --skill impact-analysisgit 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/impact-analysis)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/impact-analysis"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/impact-analysis.svg" alt="Measured on agentmods" 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.03243 |
| Opus 5 | $0.00000 | $0.01622 |
| Sonnet 5 | $0.00000 | $0.00649 |
| Haiku 4.5 | $0.00000 | $0.00324 |
Grade A, and why
impact-analysis 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 6d 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/impact-analysis Skill
Analyze the impact of architectural changes on systems, integrations, and organizational outcomes.
When to Use This Skill
Use /impact-analysis when you need to understand consequences of changes:
- Assess impact of retiring a system
- Understand cascading failures if a system goes down
- Evaluate impact of technology upgrades
- Analyze organizational impacts (skills, processes, teams)
- Create risk mitigation plans for major changes
Usage
/impact-analysis <change-description> [scope] [options]
Parameters
| Parameter | Description | Required |
|---|---|---|
change-description |
What is changing (e.g., "Retire Tableau") | Yes |
scope |
What to analyze (systems, people, process, financial, technical, all) | Optional |
--depth |
Analysis depth (quick, standard, comprehensive) | Optional |
--format |
Output format (markdown, spreadsheet, presentation) | Optional |
Workflow
Phase 1: Define Change
User describes the change:
-
What is changing?
- Retire a system
- Upgrade technology
- Replace tool
- Migrate to cloud
- Add new capability
-
Affected systems (optional - auto-detected if omitted)
- Which systems involved?
- Primary system(s) affected
- Secondary dependencies
-
Timeline (optional)
- When does change happen?
- Phase 1, Phase 2, Phase 3?
- Go-live date?
-
Scope of analysis (optional)
- Systems impact (technical)
- Integration impact (data flows)
- People impact (teams, skills)
- Process impact (workflows)
- Financial impact (cost, ROI)
- All of the above
Phase 2: Analyze Impacts
The skill:
-
Maps dependencies
- Finds all systems that depend on changed system
- Identifies integration points
- Maps data flows
-
Calculates cascading effects
- If system X goes down, what breaks?
- What is recovery path?
- How long until restoration?
-
Identifies organizational impacts
- Which teams affected?
- What skills required?
- Who needs training?
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.
- 6d ago First seen · 502 lines · 0 tokens per session scan A 0765830c2d0f
impact-analysis 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,243 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-08-30.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…