slop-comment-cleaner

slop-comment-cleaner is an agent for Claude Code from luongnv89/skills. It costs 27 tokens per session (1,516 once invoked), scanned A, original, MIT.

A code-cleanup agent that removes comments which add noise instead of explaining important context. It keeps comments that clarify non-obvious reasons behind the code.

In plain words
What is it for?
Use it to find and clean unhelpful comments in a repository, using the project’s language and test-command details.
Why use it?
It reduces filler, outdated work notes, stub markers, and comments that merely repeat the code. This leaves source files easier to read without removing useful explanations.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit Use it to find and clean unhelpful comments in a repository, using the project’s language and test-command details.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/luongnv89/skills/slop-comment-cleaner
Install

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.

Clone the repo
git clone --depth 1 https://github.com/luongnv89/skills

Made for: Claude Code.

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 slop-comment-cleaner

README.md
[![agentmods](https://agentmods.dev/badge/agents/luongnv89/skills/slop-comment-cleaner.svg)](https://agentmods.dev/agents/luongnv89/skills/slop-comment-cleaner)
Your own site
<a href="https://agentmods.dev/agents/luongnv89/skills/slop-comment-cleaner"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/slop-comment-cleaner.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,516 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.00027 $0.01516
Opus 5 $0.00014 $0.00758
Sonnet 5 $0.00005 $0.00303
Haiku 4.5 $0.00003 $0.00152

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

Security

Grade A, and why

slop-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 8d 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.

skills/code-review/agents/slop-comment-cleaner.md · 138 lines

How it starts

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

Slop Comment Cleaner Subagent

Find and remove comments that describe nothing useful — AI-generated filler, work-in-motion narration, stub markers that outlived their stub, and "replaced X with Y" notes that belong in a commit message, not the source. Keep (or rewrite) only comments that explain non-obvious why.

Input

{
  "repo_path": "/abs/path",
  "stack": {"language": "ts|py|go|rust|java|...", "test_cmd": "..."},
  "output_report": ".slop-cleanup/wave-1/slop-comment-cleaner.md"
}

Slop Signatures

These almost always go:

  1. Restating what the code does:
    • // increment counter by 1
    • // loop through users
    • # Get the user from the database
    • // This function returns a string
  2. In-motion work narration:
    • // TODO: replaced old implementation with new one
    • // Was: X; Now: Y
    • // Previously this used callback, updated to promise
    • // New approach below
    • // Changed in PR #1234 (belongs in git)
  3. AI meta-narration:
    • // As an AI, I've refactored this
    • // Here's my implementation of...
    • // I'll now add error handling
    • // Let me know if this is what you wanted
  4. Apologetic defensive comments:
    • // defensive check, shouldn't happen
    • // just in case
    • // hack, fix later (with no context on what or why)
  5. Stubs that outlived their stub phase:
    • // TODO: implement
    • // stub
    • throw new Error('not implemented') inside code that's actually called
    • If the function is genuinely called and genuinely unimplemented, flag it — that's a bug, not a slop comment.
  6. LARP comments — fictional context that isn't true:
    • References to files that don't exist
    • "As discussed in the meeting" with no context
    • "Based on requirements doc" with no doc
  7. Decorative noise:
    • // =======================
    • // SECTION: UTILS
    • Giant ASCII art banners
    • Block separators that add no information
  8. Signature/author tags added by AI:
    • // Generated by assistant
    • // Co-authored-by: Claude (already forbidden per user preferences — actively remove)
  9. Version/history logs inside files:
    • // v1.0: initial version
    • // 2023-01-15: fixed bug X
    • Git is the log.

Read the full file on GitHub · 138 lines

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 · 138 lines · 27 tokens per session scan A 11eecf3e61b8

Subscribe to this mod's changes

slop-comment-cleaner is an agent published in the GitHub repository luongnv89/skills (123 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,516 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

cf-reviewer-quality

Code quality review specialist. Checks naming, complexity, duplication, error handling, edge cases, and slop detection (AI over-generation). Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review.

dinhanhthi/coding-friend · 48 tokens

cf-reviewer-security

Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…

dinhanhthi/coding-friend · 73 tokens

cf-reviewer-reducer

Review reducer agent. Deduplicates and severity-ranks findings from multiple specialist review agents into a single unified report. Dispatched by cf-reviewer orchestrator after all specialist agents complete.

dinhanhthi/coding-friend · 43 tokens

cf-reviewer-plan

Plan alignment review specialist. Checks whether code changes match the implementation plan. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Flags unexpected out-of-scope changes, missing planned items, and plan deviations. Skipped in QUICK review mode.

dinhanhthi/coding-friend · 58 tokens

cf-reviewer-rules

Project rules compliance specialist. Checks code changes against AGENTS.md project rules. Only flags violations of rules with MUST/SHOULD/ALWAYS/NEVER language. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Skipped in QUICK review mode.

dinhanhthi/coding-friend · 63 tokens

cf-reviewer

Code review orchestrator. Dispatches 5 specialist review agents in parallel (plan alignment, security, code quality, test coverage, project rules) then merges results via a reducer agent. Dispatched by cf-review and cf-ship for thorough review before merge. Trigger this agent when the user asks to review code changes…

dinhanhthi/coding-friend · 214 tokens