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 skills/random6913/claude-code-superkit/ai-slop-cleanernpx skills add RaNDoM6913/claude-code-superkit --skill ai-slop-cleanergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/ai-slop-cleaner)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/ai-slop-cleaner"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/ai-slop-cleaner.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00938 |
| Opus 5 | $0.00013 | $0.00469 |
| Sonnet 5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
ai-slop-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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Slop Cleaner
Detect and fix common AI-generated code anti-patterns. Behavior-preserving cleanup — no logic changes, only readability and quality improvements.
Phase 0: Load Project Context
Read if exists:
AGENTS.md— project conventions, coding style.editorconfigor linter configs — formatting rules
Use this context to: distinguish project conventions from AI slop (e.g., the project MAY want verbose comments).
When to Use
- After AI-assisted implementation (post Phase 3 in dev-orchestrator)
- Before code review (catch slop before reviewers waste time on it)
- Standalone cleanup pass on existing codebase
Detection Checklist
Category 1: Redundant Comments (MOST COMMON)
// This function returns the user <- states the obvious
// Import the http package <- describes the import
// Create a new instance <- describes the constructor
// Check if the value is nil <- restates the code
// TODO: implement this <- left by AI, not real TODO
Action: Remove comments that restate what the code already says. Keep comments that explain WHY, not WHAT.
Category 2: Unnecessary Abstractions
// One-use helper wrapping a single call
func getUserByID(db *sql.DB, id string) (*User, error) {
return db.QueryRow("SELECT ...").Scan(...)
}
// Called exactly ONCE
Action: Inline one-use helpers. If a function is called once and its name matches what it does, it's noise.
Category 3: Over-Engineering
- Feature flags for non-configurable behavior
- Backwards-compatibility shims with zero consumers
- Strategy/factory patterns for 1 implementation
- Generic types where concrete types suffice
- Interface for a single implementation (no testing need)
Action: Replace with direct, simple code. YAGNI.
Category 4: Template/Boilerplate Slop
- Empty error handlers (
catch (e) {}) - Unused function parameters (especially
_placeholders) - Default switch/match cases that can't be reached
- Unnecessary type assertions on already-typed values
- Re-exporting types that are never imported from the re-export
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.
- 4d ago First seen · 119 lines · 25 tokens per session scan A 84a233ef4c33
ai-slop-cleaner is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 938 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-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…