agentmods.dev

dead-code

dead-code is a skill for Claude Code from rossumai/claude-marketplace. It costs 76 tokens per session (1,420 once invoked), scanned A, original, MIT.

A detector for unused parts of a Rossum implementation, including hooks, formulas, rules, labels, and engines. It examines a local project tree and creates a list of items that may be removed.

In plain words
What is it for?
Use it before cleanup to find candidates for deletion and create a deterministic delete-list report from the local project files.
Why use it?
It helps reduce clutter and maintenance work by identifying configuration that is no longer connected to the working setup.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the rossum-sa plugin — 33 skills, 4 hooks shipped together

not rated 5repo 4d ago A scan 76 tokens original MIT

Good fit Use it before cleanup to find candidates for deletion and create a deterministic delete-list report from the local project files.

Compare 6 skills from other repositories ↓
View source ↗ rossumai/claude-marketplace
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add rossumai/claude-marketplace
Claude Code
/plugin install rossum-sa

Made for: Claude Code.

Or install rossum-sa, the plugin that ships this one along with the rest of its 33 skills, 4 hooks.

Wrote 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.

agentmods badge for dead-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/rossumai/claude-marketplace/dead-code.svg)](https://agentmods.dev/skills/rossumai/claude-marketplace/dead-code)
Your own site
<a href="https://agentmods.dev/skills/rossumai/claude-marketplace/dead-code"><img src="https://agentmods.dev/badge/skills/rossumai/claude-marketplace/dead-code.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.01420
Opus 5 $0.00038 $0.00710
Sonnet 5 $0.00015 $0.00284
Haiku 4.5 $0.00008 $0.00142

Measured 8d ago against content hash c66eddc765ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

dead-code 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (detect.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/rossum-sa/skills/dead-code/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rossum Dead Code Analysis

Path or context: $ARGUMENTS

The Iron Rule

Every finding in the report MUST come from detect.py output. No freestanding claims. No subagent narratives. No "I think there are about N of these."

An earlier version of this skill let a subagent do freeform analysis and it invented "56 orphan formulas" with fabricated filenames. The script below exists to make that class of hallucination impossible. If you catch yourself writing a count that isn't in the script output, stop and re-run.

Workflow

  1. Source selection.

    • Local prd2 env dir (hooks/, workspaces/, optionally rules/, labels/, engines/) → use it. Prefer the most complete env (usually DEV / sandbox).
    • Check staleness with git status. If dirty or obviously old, ask the user to prd2 pull first.
    • No local tree → ask the user whether to pull via mcp__plugin_rossum-sa_rossum-api__* read-only tools into a temporary dir mirroring the prd2 layout, then run the script against that.

  2. Run the detector and show the output:

    python3 ${CLAUDE_PLUGIN_ROOT}/skills/dead-code/detect.py <env_dir>

    Output is markdown. Present it verbatim (or lightly framed). Don't re-paraphrase findings as aggregate prose — names are what's actionable.

  3. Verify label candidates against the API. The script's "Label candidates" section lists labels with no rule references, but labels can also be applied manually by users — so rule-unreferenced ≠ dead. For each candidate, call rossum_search_annotations with labels=<id> and max_results=1:

    • 0 annotations → the label really is unused. Keep the finding, mark it as confirmed.
    • ≥1 annotations → the label is in manual use. Remove it from the report and note the annotation count.

    Do this before presenting. If the MCP is not connected, say so and leave the label section marked "unverified — run rossum_set_token and re-check".

  4. Spot-check at least 2 other findings on disk before presenting. Examples:

    • Orphan hook: open the JSON and confirm queues: [].
    • Unused engine: rg "engines/<id>" <env>/workspaces/ returns 0 hits.
    • Dead rule: open the JSON and confirm enabled: false or queues: [].

Read the full file on GitHub · 88 lines

Files

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.

Changes

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.

  1. 8d ago First seen · 88 lines · 76 tokens per session scan A c66eddc765ad

Subscribe to this mod's changes

dead-code is a skill published in the GitHub repository rossumai/claude-marketplace (5 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 1,420 once invoked, about $0.0004 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.

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens