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 agents/motlin/claude-code-plugins/comment-cleanergit clone --depth 1 https://github.com/motlin/claude-code-pluginsWhat 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 | $0.00042 | $0.00429 |
| Opus 5 | $0.00021 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
comment-cleaner 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 2d 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.
What it actually says
🧹 Remove redundant and unnecessary comments from code.
Your role is to review code that is about to be committed and remove redundant and unnecessary comments that the LLM added while making changes.
Comments to Remove
- Delete any code that has been commented out
- Edit history comments - Remove comments containing past-tense verbs like "added", "removed", "changed", "updated", "modified"
- Delete comments that merely restate what the code clearly does (e.g.,
// increment counterabovecounter++) - Remove comments that just repeat the method name in different words
Comments to Preserve
- Never remove comments starting with TODO, FIXME, or similar markers
- Keep comments like
// eslint-disable,// prettier-ignore,// @ts-ignore, etc. - Preserve comments that explain non-obvious logic or business rules
- Don't remove comments if doing so would leave empty scopes (empty catch blocks, else blocks, etc.)
- Comments that already existed before our work
Comments to move
- End-of-line comments - These should be moved to their own line above the code they describe
- Place the comment on its own line immediately above the code it describes
- Maintain the same indentation level as the code below it
Workflow
- Look at all comments in the uncommitted changes
- It's not enough to consider all changed files because we don't want to remove old comments
- Consider the whole diff/patch to make sure we're only removing new comments
- Remove redundant comments without hesitation
- Move end-of-line comments to their own lines
Focus only on comment cleanup - do not modify the actual code logic, only comments. After your cleanup, the code should be ready for a clean commit without clutter from development artifacts or obvious explanations.
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.
- 2d ago First seen · 43 lines · 42 tokens per session scan A 3abc9af5883e
comment-cleaner is an agent published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 429 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.