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/jerseycheese/agent-skills/dead-code-cleanupnpx skills add jerseycheese/agent-skills --skill dead-code-cleanupgit clone --depth 1 https://github.com/jerseycheese/agent-skillsWrote 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/jerseycheese/agent-skills/dead-code-cleanup)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/dead-code-cleanup"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/dead-code-cleanup.svg" alt="Measured on agentmods" 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.00105 | $0.05381 |
| Opus 5 | $0.00053 | $0.02691 |
| Sonnet 5 | $0.00021 | $0.01076 |
| Haiku 4.5 | $0.00011 | $0.00538 |
Grade A, and why
dead-code-cleanup 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 694 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Cleanup
Overview
Systematically identifies dead, orphaned, and trivial code across the codebase including components, tests, and Storybook stories. Validates that code is truly unused before removal to prevent breaking changes. Also removes stories that provide no documentation value or only demonstrate rare edge cases.
What Qualifies as Dead/Trivial Code
Dead/Orphaned Code
- Components never imported - React components with no imports anywhere
- Unused utilities - Functions/modules with no consumers
- Orphaned tests - Tests for deleted/moved components
- Orphaned stories - Storybook stories for deleted/moved components
- Commented-out code - Code blocks that have been commented out
- Debug code - Console logs, debug flags, temporary test utilities
Trivial Tests
- Tests that always pass - Tests with no real assertions or mocked to always succeed
- Empty render tests - Tests that only verify component renders without crashing
- Pointless existence tests - Tests that check if a component is defined
- Snapshot-only tests - Tests with only snapshots and no behavior validation
- Duplicate tests - Multiple tests checking the same exact behavior
Trivial Storybook Stories
- No-value stories - Stories that show the exact same thing as another story
- Default-only stories - Stories that only render component with no props (when default story exists)
- Edge case stories - Stories demonstrating extremely rare scenarios unlikely to occur
- Duplicate states - Multiple stories showing identical visual states
- Over-specification stories - Stories for every tiny prop variation that adds no documentation value
- Obvious behavior stories - Stories showing behavior that's self-evident from the component
Examples of trivial stories to remove:
// ❌ Trivial - just default with no props (when Default story exists)
export const Empty: Story = {
args: {},
};
// ❌ Trivial - rare edge case nobody will encounter
export const WithExactly47Characters: Story = {
args: {
text: "This string has exactly forty-seven chars!",
},
};
// ❌ Trivial - duplicate of existing state
export const LoadingState: Story = {
args: { loading: true },
};
export const IsLoading: Story = { // Duplicate!
args: { loading: true },
};
// ❌ Trivial - no documentation value
export const WithPadding5: Story = {
args: { padding: 5 },
};
export const WithPadding6: Story = {
args: { padding: 6 },
};
export const WithPadding7: Story = {
args: { padding: 7 },
};
// ✅ Keep - demonstrates important state
export const ErrorState: Story = {
args: {
error: "Failed to load data",
onRetry: fn(),
},
};
// ✅ Keep - shows important variant
export const WithLongContent: Story = {
args: {
children: "Very long content that tests text wrapping...",
},
};
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.
- 5d ago First seen · 694 lines · 105 tokens per session scan A 868a8a30d484
dead-code-cleanup is a skill published in the GitHub repository jerseycheese/agent-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 5,381 once invoked, about $0.0005 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-31.
Other skills, from other repositories
engram-rebuild
이미 설치된 engram 환경에 개발 변경을 적용한다. dev-rebuild.ps1 로 충분한지 INSTALL.ps1 전체를 돌려야 하는지 판단하고 실행한다. 트리거 — 재빌드, 리빌드, dev 변경 적용, 설치본에 반영, overlay 재시작, exe 갱신, "고친 거 확인하려면 뭐 돌려야 해", rebuild, redeploy.
orchestrate
Run Engram's Orchestrator-Planner-Coder-Servant workflow for multi-step development, refactors, or research-plus-implementation tasks that need an acceptance contract and independent verification. Trigger for "orchestrate", delegation requests, planning then implementation, or complex multi-step development. Do not…
engram-new-session
Skill "engram-new-session" from JJHbrams/Project-AMBER, covering engram 말풍선 — 새 세션 시작, 실행 절차 and 규칙.
env-scanner
Scan and audit Gemini CLI, Claude Code, Antigravity, Continue, Windsurf, JetBrains AI, and OpenCode environments. Discovers configurations, audits memory tiers, detects skill extraction state, analyzes behavioral tool chains, checks policy governance (v0.40+), and suggests reusable skills with evidence gating.…
scan
Scan your AI coding tool ecosystem — Gemini CLI, Claude Code, Antigravity (Desktop, CLI, IDE), Continue, Windsurf, JetBrains AI, OpenCode. Produces a maturity score, advisory recommendations, and optionally generates reusable SKILL.md files from your conversation patterns. Use when the user asks to audit their…
engram-close-session
Engram의 명시적 세션 종료·수동 반성을 수행한다. 트리거: 세션 종료, 대화 종료, 수고, 끝, /reflect, 반성, close session. 중간 메모리/Wiki 정리는 이 skill이 아니라 engramsummarizesession을 사용한다.