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.
/plugin marketplace add bengous/claude-code-plugins/plugin install clean-commentsWrote 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/bengous/claude-code-plugins/clean-comments)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/clean-comments"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/clean-comments/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/bengous/claude-code-plugins/clean-comments"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/clean-comments.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.00108 | $0.03126 |
| Opus 5.5 | $0.00043 | $0.01250 |
| Sonnet 5.5 | $0.00022 | $0.00625 |
| Haiku 4.5 | $0.00011 | $0.00313 |
Grade A, and why
clean-comments 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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Comments
The cheap one is noise: a comment that restates the line below it. It wastes a reader's second, nothing more.
The expensive one is a comment that LIES: a path that moved, a count that grew, a "TEMPORARY" that shipped, a "stubbed" the code refutes. It sends the next reader — human or agent — toward a wrong decision. On a real audit it outnumbered pure paraphrase in cost by a wide margin, and no grid that only asks "does this restate the code?" ever catches it.
So this skill judges truth as well as usefulness, and it protects the comments that carry a why or a constraint — those are an asset, not debt.
Budget (non-negotiable)
- Size batches by content volume, not file count: target ~200k tokens of file content per hunter (bytes / 4), never more than ~300k — past that the context is too full and error rates climb.
- Hunter count = ceil(total volume / 200k). Most repos need 1 to 3 hunters.
- At most 4 hunters run concurrently.
- If the estimate exceeds 4 hunters (~1M tokens in scope): STOP. Show the file count,
the estimated volume, the comment-line total (probe
--count), and the hunter count. Launch nothing before the user explicitly confirms. After confirmation, run waves of 4, total announced up front. - A hunter NEVER spawns a subagent, and never invokes
claudethrough Bash. No exception, including "just to verify". - These values are defaults: the user can override them in the prompt, or a repo can override the hunter (see Extension points).
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 First seen · 281 lines · 108 tokens per session scan A 7ccf0641e975
clean-comments is a skill published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 3,126 once invoked, about $0.0004 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 skills, from other repositories
verify-change
A change-checking skill that reviews code differences and checks whether related documentation, tests, and records were updated.
verify-module
A module-checking skill that scans a project’s folders, code, and documentation. It expects each module to include a README.md and DESIGN.md, which explain how the module is used and why it was designed that way.
verify-quality
A code-quality checker that measures complexity, size, naming, and common code smells. It reports problems such as duplicated code, unused code, and overly long functions.
planning
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. If create-tasks is not visible, load it via loadtool (search "create tasks"). Do NOT use for new one-off workflows, single-workflow…
criticism-self-criticism
A structured review method for examining completed work, criticism, and repeated mistakes. It focuses on specific evidence, causes, effects, and practical improvements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.