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 sethdford/claude-skills --skill change-impact-analysisgit clone --depth 1 https://github.com/sethdford/claude-skillsWrote 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/sethdford/claude-skills/change-impact-analysis)<a href="https://agentmods.dev/skills/sethdford/claude-skills/change-impact-analysis"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/change-impact-analysis/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/sethdford/claude-skills/change-impact-analysis"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/change-impact-analysis.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.00032 | $0.00604 |
| Opus 5.5 | $0.00013 | $0.00242 |
| Sonnet 5.5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
change-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 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Impact Analysis
Systematically analyze impacts of architectural changes to predict risk and plan safe rollout.
Context
You are analyzing impact of a major change. Trace affected systems, identify risks, plan mitigation. Read current dependency graph, deployment practices, system health metrics.
Domain Context
Based on change management and impact analysis frameworks:
- Direct Impact: System directly modified. Code changes, performance changes, behavior changes.
- Indirect Impact: Dependent systems affected. Database schema change affects clients. Service API change affects all callers. Message format change affects consumers.
- Risk Assessment: What could go wrong? Cascading failures? Data loss? Performance regression? Unavailability of critical path?
- Rollback Plan: If change goes wrong, can you revert quickly? What data consistency issues might occur?
Instructions
-
Trace Dependencies: What systems depend on the component you're changing? Use dependency graph tools (source analysis, API scanning). Interview teams.
-
Assess Direct Impact: For the component itself, what's changing? Behavior? Performance? Data model? How does change affect invariants, contracts, SLAs?
-
Assess Indirect Impact: For each dependent system, how does change affect it? Can they continue working with new interface? Will they need code changes? Testing?
-
Calculate Risk Score: How many systems affected? (x10 multiplier per additional system). How critical are those systems? (x5 for customer-facing, x2 for internal). Estimate blast radius.
-
Plan Mitigation: For high-risk changes, plan phased rollout (10% users, 50%, 100%). Parallel run (old and new simultaneously). Comprehensive testing and monitoring. Runbook for quick rollback.
Anti-Patterns
- Change Without Impact Analysis: Architect makes change unilaterally. Result: breaks production, cascading failures. Guard: Mandatory impact analysis before major changes; design review.
- Underestimating Blast Radius: Assume only 1-2 systems affected. Result: surprises. Guard: Systematic dependency tracing; interview teams; over-estimate.
- No Rollback Plan: Assume change succeeds. Result: stuck if it fails. Guard: Practice rollbacks; measure rollback time; have detailed procedure.
- Ignoring Monitoring: Make change, wait for problems to surface. Result: incidents. Guard: Comprehensive monitoring; metrics for correctness, performance, errors; alert on anomalies.
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 · 47 lines · 32 tokens per session scan A 74fd8c95aff0
change-impact-analysis is a skill published in the GitHub repository sethdford/claude-skills (45 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 604 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
design-system-architect
Expert guide for designing, building, and maintaining scalable UI design systems with design tokens, headless primitives, Material Design 3 (M3), Tailwind v4 @theme, Modern Web Guidance, and WCAG 2.2 accessibility.
zero-to-prod-orchestrator
Master orchestrator to build an application from scratch to a production-ready release, enforcing strict step-by-step progression and continuous documentation / Orkestrator utama untuk membangun aplikasi dari nol hingga rilis siap produksi dengan dokumentasi bertahap.
file-upload-media-expert
Expert guide for file uploads (S3, R2, Supabase Storage), presigned URLs, image/video processing, CDN optimization, and media pipeline architecture / Panduan ahli untuk upload file (S3, R2, Supabase Storage), presigned URL, pemrosesan gambar/video, optimasi CDN, dan arsitektur pipeline media.
email-notification-expert
Expert guide for transactional email (Resend, Postmark, SES), React Email templates, in-app notifications, and unified communication pipelines / Panduan ahli untuk email transaksional (Resend, Postmark, SES), template React Email, notifikasi in-app, dan pipeline komunikasi terpadu.
firebase-security-expert
Firebase security expert to audit Security Rules (Firestore/Realtime Database/Storage), authentication, API keys, data leakage prevention, and App Check configuration / Ahli keamanan Firebase untuk audit Security Rules (Firestore/Realtime Database/Storage), autentikasi, API keys, pencegahan kebocoran data, dan…
go-programming-expert
Expert-level skill for Go programming (Go 1.24+ / 1.25+). Covers Swiss Table maps, weak pointers, synctest concurrency testing, tool directives, sqlc, net/http, and microservices in English and Indonesian.