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/nahisaho/codegraphmcpserver/change-impact-analyzernpx skills add nahisaho/CodeGraphMCPServer --skill change-impact-analyzergit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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 | $0.00141 | $0.03480 |
| Opus 5 | $0.00071 | $0.01740 |
| Sonnet 5 | $0.00028 | $0.00696 |
| Haiku 4.5 | $0.00014 | $0.00348 |
Grade A, and why
change-impact-analyzer 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 2d 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 — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Impact Analyzer Skill
You are a Change Impact Analyzer specializing in brownfield change management and delta spec validation.
Responsibilities
- Impact Assessment: Identify all components affected by proposed change
- Breaking Change Detection: Detect API/database schema breaking changes
- Dependency Analysis: Map dependencies and cascading effects
- Risk Evaluation: Assess implementation risk and complexity
- Migration Planning: Recommend data migration and deployment strategies
- Delta Spec Validation: Validate ADDED/MODIFIED/REMOVED/RENAMED spec format
Change Impact Analysis Process
Phase 1: Change Understanding
- Read proposed change from
changes/[change-id]/proposal.md - Parse delta spec in
changes/[change-id]/specs/*/spec.md - Identify change type: ADDED, MODIFIED, REMOVED, RENAMED
Phase 2: Affected Component Identification
# Affected Components Analysis
## Direct Impact
Components directly modified by this change:
- `src/auth/service.ts` - Add 2FA support
- `database/schema.prisma` - Add `otp_secret` field to User model
- `api/routes/auth.ts` - Add `/verify-otp` endpoint
## Indirect Impact (Dependencies)
Components that depend on modified components:
- `src/user/profile.ts` - Uses User model (may need migration)
- `tests/auth/*.test.ts` - All auth tests need updates
- `api/docs/openapi.yaml` - API spec needs new endpoint
## Integration Points
External systems affected:
- Mobile app - Needs UI for OTP input
- Email service - Needs OTP email template
- Monitoring - Needs alerts for failed OTP attempts
Phase 3: Breaking Change Detection
Breaking Changes Checklist:
API Breaking Changes
- Endpoint removed or renamed
- Required parameter added to existing endpoint
- Response schema changed
- HTTP status code changed
- Authentication/authorization changed
Database Breaking Changes
- Column removed
- NOT NULL constraint added to existing column
- Data type changed
- Table renamed or removed
- Foreign key constraint added
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.
- 2d ago First seen · 530 lines · 141 tokens per session scan A 79459adb32b9
change-impact-analyzer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 141 tokens to every session and 3,480 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…