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 James-Chahwan/repo-graph --skill repo-graph-impactgit clone --depth 1 https://github.com/James-Chahwan/repo-graphWrote 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/james-chahwan/repo-graph/repo-graph-impact)<a href="https://agentmods.dev/skills/james-chahwan/repo-graph/repo-graph-impact"><img src="https://agentmods.dev/badge/skills/james-chahwan/repo-graph/repo-graph-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/james-chahwan/repo-graph/repo-graph-impact"><img src="https://agentmods.dev/badge/skills/james-chahwan/repo-graph/repo-graph-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.00047 | $0.00313 |
| Opus 5 | $0.00023 | $0.00156 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
repo-graph-impact 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 12d 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.
What it actually says
repo-graph impact
Know what a change touches before you make it.
When to use
- Before modifying or deleting a function, route, or component.
- "What breaks if I change this?" / "who uses this?"
Steps
- Call
impactwithnodes=<name>.direction=forward(what it affects, the default sense) /backward(what it depends on / who uses it) /both;depthis 1–10. Pass several comma-separated nodes (e.g. every symbol in a diff) for the unified blast radius in one call. Each row shows avia <reason>edge label and a⊘marker when the engine finds the node unreachable from any entry point — likely dead code. Addlive_only=trueto drop those. - For just the immediate wiring, call
impactatdepth=1withdirection=both— direct callers and callees one hop out (this replaces the oldneighbourstool). - Report affected nodes by tier (entry / service / handler / data), and call out anything a plain grep would miss — transitive and cross-file dependents, and anything flagged
⊘.
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.
- 12d ago First seen · 20 lines · 47 tokens per session scan A 9959e8e2e8e5
repo-graph-impact is a skill published in the GitHub repository James-Chahwan/repo-graph (15 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 313 once invoked, about $0.0002 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…