Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anortham/julie-pluginnpx agentmods add skills/anortham/julie-plugin/dead-code-auditWrote 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/anortham/julie-plugin/dead-code-audit)<a href="https://agentmods.dev/skills/anortham/julie-plugin/dead-code-audit"><img src="https://agentmods.dev/badge/skills/anortham/julie-plugin/dead-code-audit/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/anortham/julie-plugin/dead-code-audit"><img src="https://agentmods.dev/badge/skills/anortham/julie-plugin/dead-code-audit.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.00037 | $0.01370 |
| Opus 5.5 | $0.00015 | $0.00548 |
| Sonnet 5.5 | $0.00007 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
dead-code-audit 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 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.
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
100% identical to dead-code-audit — 0 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Audit
Use Julie's index as evidence, then verify with Julie tools before any edit. A zero-reference row is a lead, not a verdict.
Scope
This skill is for Julie development:
- dead code and stale helper audits
- code referenced only by tests
- public APIs with no product callers
- graph linkage gaps that look like dead code
- cleanup campaigns before deletion, privatization, or module splitting
Do not use this as a blind deletion workflow. Dynamic dispatch, trait impls, CLI entry points, MCP handlers, generated fixtures, parser registries, macro usage, and cross-language extraction paths all create false positives.
Inventory
- Get the current workspace id:
manage_workspace(operation="status")
- Run the bundled inventory script from the repo root:
python3 .claude/skills/dead-code-audit/scripts/dead_code_inventory.py --workspace-id <workspace_id> --limit 40
Use --db <path> if the workspace's index is not under the default ~/.julie/indexes/<workspace_id>/ location (e.g. a standalone .julie/ project index). Use --json when another script will postprocess the result. The default report excludes fixtures, docs, examples, and data/config languages. Add --include-fixtures or --include-data-languages when that scope matters.
- Also run early-warning signals:
./target/debug/julie-server signals --workspace . --fresh --limit 40
Build debug first if needed. Keep this read-only.
Triage Labels
Assign one label to each candidate:
| Label | Meaning |
|---|---|
delete |
No product reachability, no external dispatch role, no useful test-only value |
make-private |
Used in product code, but exported wider than needed |
merge-into-caller |
Single product caller and no independent concept |
test-fossil |
Product symbol exists only to satisfy tests |
graph-gap |
Julie failed to link real product usage |
keep |
Valid entry point, trait hook, registry item, dynamic target, or public surface |
needs-design-review |
Risky or ambiguous enough to discuss before edits |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 37fb62644f44
- 2mo ago First seen · 153 lines · 37 tokens per session scan A 52e37d55b8cf
dead-code-audit is a skill published in the GitHub repository anortham/julie-plugin (2 stars, last pushed 27d ago), licensed MIT. It adds 37 tokens to every session and 1,370 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dead-code-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
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.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…