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/theagenticguy/opencodehub/codehub-impact-analysisnpx skills add theagenticguy/opencodehub --skill codehub-impact-analysisgit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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.00058 | $0.01529 |
| Opus 5 | $0.00029 | $0.00764 |
| Sonnet 5 | $0.00012 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
codehub-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 yesterday.
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.
This is a copy
97% identical to opencodehub-impact-analysis — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impact Analysis with OpenCodeHub
When to Use
- "Is it safe to change this function?"
- "What will break if I modify X?"
- "Show me the blast radius."
- "Who uses this code?"
- Before committing or merging a non-trivial change.
Decision Tree
Is the target a symbol (function, class, method, property)?
└─ yes → mcp__codehub__impact
Is the target an HTTP route or API endpoint?
└─ yes → mcp__codehub__api_impact + mcp__codehub__route_map
Is the change a response-shape edit on a route?
└─ yes → mcp__codehub__shape_check (find consumer key-access mismatches)
Is the target a dependency version bump?
└─ yes → mcp__codehub__dependencies + mcp__codehub__license_audit
Want to see what the working tree currently touches?
└─ yes → mcp__codehub__detect_changes
Workflow
1. mcp__codehub__impact({ name, direction: "upstream", repo }) → Dependents of the target
2. Read confidenceBreakdown → Trust the confirmed count
3. If HTTP-adjacent: mcp__codehub__api_impact + shape_check → Route + shape mismatches
4. mcp__codehub__detect_changes → Map the current diff to flows
5. Assess risk tier and write the summary
If the context envelope warns the index is stale, run
codehub analyzefirst — stale impact results are worse than no impact results.
Checklist
- [ ] mcp__codehub__impact({ name, direction: "upstream", repo })
- [ ] Review byDepth.d1 first — these WILL BREAK
- [ ] Read confidenceBreakdown; demand confirmed >= heuristic for destructive calls
- [ ] Filter to confidence >= 0.9 if the target is load-bearing (auth, payments, data integrity)
- [ ] If target is a Route: mcp__codehub__api_impact + mcp__codehub__shape_check
- [ ] mcp__codehub__detect_changes to map the current diff to affected processes
- [ ] Produce a risk tier and a one-paragraph summary
Understanding impact output
Risk levels map to blast-radius tiers:
| Depth | Risk Level | Meaning |
|---|---|---|
| d=1 | WILL BREAK | Direct callers / importers / overrides |
| d=2 | LIKELY AFFECTED | One hop through d=1 |
| d=3 | MAY NEED TESTING | Two hops — transitive effects |
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.
- yesterday First seen · 152 lines · 58 tokens per session scan A 42916cf960c0
codehub-impact-analysis is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,529 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to opencodehub-impact-analysis, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…