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 magic5644/Graph-It-Live --skill dead-code-huntergit clone --depth 1 https://github.com/magic5644/Graph-It-LiveWrote 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/magic5644/graph-it-live/dead-code-hunter)<a href="https://agentmods.dev/skills/magic5644/graph-it-live/dead-code-hunter"><img src="https://agentmods.dev/badge/skills/magic5644/graph-it-live/dead-code-hunter/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/magic5644/graph-it-live/dead-code-hunter"><img src="https://agentmods.dev/badge/skills/magic5644/graph-it-live/dead-code-hunter.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.00165 | $0.02367 |
| Opus 5.5 | $0.00066 | $0.00947 |
| Sonnet 5.5 | $0.00033 | $0.00473 |
| Haiku 4.5 | $0.00016 | $0.00237 |
Grade A, and why
dead-code-hunter 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 today.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Hunter
Systematic scan of the dependency graph to surface orphan symbols and unreferenced files. Produces a ranked, safety-annotated deletion plan powered by Graph-It-Live.
CLI and Capability Discovery
Prefer the Graph-It CLI. At the first activation of any Graph-It skill in a session, check
graph-it --version when the CLI and terminal are available; use only its existing newer-version
notice and do not poll npm. Share discovery, version, and update decisions across Graph-It skills
for the session. Run graph-it tool --list once, consult graph-it --help or command help as
needed, and refresh only when the CLI/version, server, or workspace changes or a requested tool is
unknown. Examples are illustrative, not a fixed inventory. Do not install automatically. If the
CLI is unavailable or unsuitable, use MCP only when the connected host advertises an equivalent
tool and its schema; otherwise explain the gap. graph-it tool <name> invokes analysis directly
through CLI; graph-it serve starts MCP. CLI --format and MCP response_format are distinct.
If the CLI reports a newer version, interactive use requires explicit positive confirmation before
running graph-it update; silence, timeout, refusal, non-TTY, or generic Agent mode is not consent.
When automatic mode is explicitly enabled and pre-authorized, default the update decision to yes and
run graph-it update without another prompt. After success, refresh the version and --list,
invalidate cached capabilities, and advise that a running MCP server needs a host-authorized restart.
On failure, keep using the existing CLI only if it remains usable; otherwise explain the failure
and stop CLI analysis. Warn briefly and do not retry in a loop.
When to Use
- Before a major refactor — clean up before you restructure
- After removing a feature — confirm nothing is left dangling
- Periodic code hygiene pass on a growing codebase
- Before onboarding a new developer — reduce noise in the codebase
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.
- today Changed · +11 lines 662b85aa452b
- 6d ago Changed · -3 lines e6ccb728d199
- 9d ago Changed · +2 lines 42d95f629473
- 27d ago First seen · 203 lines · 165 tokens per session scan A 507d038408ad
dead-code-hunter is a skill published in the GitHub repository magic5644/Graph-It-Live (56 stars, last pushed today), licensed MIT. It adds 165 tokens to every session and 2,367 once invoked, about $0.0007 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-09-13.
Other skills, from other repositories
devhost-debug
Inspect this extension running in the Antigravity IDE Extension Development Host (F5) - sidebar DOM and screenshots, extension host state through non-pausing logpoints, the dev host's own Language Server and log, and Auto-Accept dry runs. Use after changing UI, webview messages, connection or parsing, or automation…
debugging-and-error-recovery
A systematic debugging procedure for finding the underlying cause of failed tests, broken builds, bugs, and unexpected behavior. It emphasizes reproducing the problem, preserving evidence, fixing the cause, and checking the fix.
gemini-3-prompting
Guidance for writing effective prompts for Antigravity (agy) / Gemini 3 models.
agy-result-handling
Internal guidance for presenting agy output back to the user.
debugging-and-error-recovery
Guides systematic root-cause debugging with hard rules against guess-fixes and symptom suppression. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Triggers on "this is broken", "tests are failing", "why doesn't this work", or any error output.
debugging-master
Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken, investigate, root cause, why is this happening, figure out, troubleshoot, doesn't work, unexpected behavior, debugging, root-cause…