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 BostonOrange/claude-code-framework --skill impactgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/impact)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/impact"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/impact/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/bostonorange/claude-code-framework/impact"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/impact.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.00068 | $0.01190 |
| Opus 5.5 | $0.00027 | $0.00476 |
| Sonnet 5.5 | $0.00014 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade B, and why
impact scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
description: On-demand precise impact analysis for a symbol or file before changing it. Spawns impact-analyzer to grep callers, classify the cascade (direct/indirect/test-only), and produce a confidence-scored report. Di How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impact — On-Demand Cascade Analysis
Before making a confident-but-wrong change to a function, class, or file, run /impact to see what would break.
/impact answers questions like "if I change the return type of requireAuth, what breaks?" — without you having to grep callers, read each one, and reason about cascades by hand. Output is a structured report at .claude/state/impact-<hash>.md plus a short summary.
This complements .claude/state/architecture.md:
- architecture.md is the broad map (module boundaries, dependency direction, top-10 hotspots) refreshed by
/improveeach session /impact <symbol>is the focused drill-down for a specific change you're about to make
Usage
/impact <file> analyze every exported symbol in the file
/impact <file>:<symbol> analyze just that symbol
/impact <symbol> bare symbol; spawns analyzer to find definition first
/impact --refresh <target> ignore cache; re-run analysis
Examples:
/impact lib/auth/middleware.ts
/impact lib/auth/middleware.ts:requireAuth
/impact requireAuth
/impact AccountTriggerHandler.cls:beforeInsert # Apex
Process
Phase 1: Spawn impact-analyzer
Run impact analysis on <target>. Locate the definition, find direct callers,
classify references (direct/type/test), trace second-order public callers
(depth=2 max), score confidence, write the report to .claude/state/impact-<hash>.md.
End with the surface summary.
The agent is read-only by tool restriction (Read, Glob, Grep, Bash — no Edit/Write). Its only filesystem write is the report file.
Phase 2: Surface to user
Read the agent's summary output. Show:
- Total references + breakdown (direct / type / test)
- Confidence level + top caveat
- Top 3 most-impacted files
- Recommendation one-liner
- Path to the full report
Phase 3: Hand-off
If the user is iterating on a change:
- "Confidence is high — proceed; the test suite at
<paths>should catch regressions" - "Confidence is medium — review the second-order callers in
.claude/state/impact-<hash>.mdbefore merging" - "Confidence is low — string-keyed lookups detected; grep can't see them all. Consider running tests in addition"
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 · 103 lines · 68 tokens per session scan B 958c27f34ab6
impact is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 1,190 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.