Borrowing it
Nothing to install: this file belongs to kirti12025/gitlab-mcp. 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/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/skills/ai-slop-cleaner/SKILL.mdgit clone --depth 1 https://github.com/kirti12025/gitlab-mcpWrote 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/kirti12025/gitlab-mcp/ai-slop-cleaner)<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/ai-slop-cleaner"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/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/kirti12025/gitlab-mcp/ai-slop-cleaner"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/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 10d 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.
- 10d ago First seen · 45 lines · 46 tokens per session scan A 430910f14205
ai-slop-cleaner is a skill published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 1mo 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…