Borrowing it
Nothing to install: this file belongs to jmstar85/oh-my-githubcopilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmstar85/oh-my-githubcopilot/main/.github/skills/ai-slop-cleaner/SKILL.mdgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/ai-slop-cleaner)<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/ai-slop-cleaner"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/ai-slop-cleaner/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/jmstar85/oh-my-githubcopilot/ai-slop-cleaner"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/ai-slop-cleaner.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.00046 | $0.00333 |
| Opus 5 | $0.00023 | $0.00167 |
| Sonnet 5 | $0.00009 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00033 |
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 9d 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.
This is a copy
100% identical to ai-slop-cleaner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AI Slop Cleaner
Clean AI-generated code slop without changing behavior. Deletion-first workflow with regression safety.
When to Use
- Code that works but feels bloated, repetitive, or over-abstracted
- Duplicate logic, dead code, wrapper layers, boundary leaks
--reviewfor reviewer-only mode (no changes, just findings)
When NOT to Use
- New feature build or product change
- Broad redesign
- Behavior is unclear and untestable
Principles
- Preserve behavior unless explicitly asked for changes
- Delete before refactoring — removal is safest
- Scope-bounded: only clean what was specified
- Regression-safe: verify tests pass after every change
Slop Signals
- Unnecessary wrapper functions
- Duplicated logic across files
- Over-abstracted single-use helpers
- Dead code / unreachable branches
- Excessive comments restating obvious code
- Premature abstractions (used only once)
Workflow
- Identify target files/scope
- Run existing tests (baseline)
- Apply deletions first (dead code, unused imports)
- Simplify remaining code (reduce nesting, merge duplicates)
- Re-run tests after each change
- Report what was cleaned and verification results
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.
- 9d ago First seen · 45 lines · 46 tokens per session scan A 430910f14205
ai-slop-cleaner is a skill published in the GitHub repository jmstar85/oh-my-githubcopilot (155 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 333 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ai-slop-cleaner, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.