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.
git clone --depth 1 https://github.com/lukaskellerstein/claude-my-marketplaceWrote 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/agents/lukaskellerstein/claude-my-marketplace/dead-code-analyzer)<a href="https://agentmods.dev/agents/lukaskellerstein/claude-my-marketplace/dead-code-analyzer"><img src="https://agentmods.dev/badge/agents/lukaskellerstein/claude-my-marketplace/dead-code-analyzer/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/agents/lukaskellerstein/claude-my-marketplace/dead-code-analyzer"><img src="https://agentmods.dev/badge/agents/lukaskellerstein/claude-my-marketplace/dead-code-analyzer.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.00160 | $0.01471 |
| Opus 5.5 | $0.00064 | $0.00588 |
| Sonnet 5.5 | $0.00032 | $0.00294 |
| Haiku 4.5 | $0.00016 | $0.00147 |
Grade A, and why
dead-code-analyzer 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 151 lines · 160 tokens per session scan A a1c5f015d6f0
dead-code-analyzer is an agent published in the GitHub repository lukaskellerstein/claude-my-marketplace (2 stars, last pushed 1mo ago), with no licence file. It adds 160 tokens to every session and 1,471 once invoked, about $0.0006 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-08-31.
Other agents, from other repositories
code-resolver
Re-checks prior findings after a code fix. Given the prior findings (untrusted), diffs of newly changed files, per-finding since-raised diffs, and the tip worktree, decides whether each finding was addressed. Not for general questions.
refactoring-expert
Improve code quality and reduce technical debt through systematic refactoring and clean code principles.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
ia-performance-oracle
Analyzes code for performance bottlenecks, algorithmic complexity, database queries, memory usage, and scalability. Use after implementing features or when performance concerns arise.
ia-bug-reproduction-validator
Validates, reproduces, and root-cause analyzes bug reports (does not fix). Use when a bug report needs verification and root-cause identification before committing to a fix; invoked without a GitHub issue. For issue-linked reproduction use /ia-reproduce-bug.
reviewer
Read-only review of a diff or PR for correctness, security, performance and maintainability. Returns path:line findings and a verdict. Use before merging a change.