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/asyrafhussin/agent-skills/code-slopnpx skills add AsyrafHussin/agent-skills --skill code-slopgit clone --depth 1 https://github.com/AsyrafHussin/agent-skillsWrote 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/asyrafhussin/agent-skills/code-slop)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/code-slop"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/code-slop.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.1 | $0.00110 | $0.03012 |
| Opus 5 | $0.00055 | $0.01506 |
| Sonnet 5 | $0.00022 | $0.00602 |
| Haiku 4.5 | $0.00011 | $0.00301 |
Grade A, and why
code-slop 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 6d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Slop Detection
Taste-level review of code for AI-generated patterns. Contains 24 rules across 6 categories covering comments, naming, over-engineering, defensive overdose, test slop, and style fingerprints. Where technical-debt measures quantitative code debt (complexity, duplication, CVEs), this skill measures the qualitative failure mode: code that passes every metric but reads like a tutorial blog post, not like a human wrote it.
Metadata
- Version: 1.0.0
- Scope: PHP / Laravel + TypeScript / React (Node)
- Rule Count: 24 rules across 6 categories
- License: MIT
Why this skill exists
Industry data on AI-assisted code (GitClear 2025, cURL bug-bounty shutdown 2025, arXiv 2510.03029):
- Refactoring collapsed from 25% to <10% of changes
- Copy-paste surged 8.3% → 12.3%; code duplication rose ~8x
- Code-smell rates +42–85% over human baselines
- 82% of AI PRs use generic catch blocks that don't distinguish error types
- 76% miss timeouts on external calls
None of this fails a typical CI lint. It just makes the codebase slowly unmaintainable. This skill is the lens for catching it before it ships.
The core insight: reading cost > writing cost now. The cost of writing code collapsed; the cost of reading it didn't. Code you can't quickly understand is slop, even if it works.
How to Audit
When the user asks "review for AI slop", "audit code-quality taste", or "find AI patterns" — run through this skill's rules as a checklist against the changed files (PR diff) or full repo.
Audit Step 1: Determine Scope
- If a PR diff is provided: audit only files changed in the diff
- If files are named: audit those
- If no scope: audit the whole repo, prioritized by recently-touched files (most likely AI output)
Audit Step 2: Detect Stack
| Signal | Stack |
|---|---|
composer.json + artisan |
PHP / Laravel |
package.json (with TypeScript/React deps) |
Node / TypeScript / React |
| Both present | Laravel + Inertia + React |
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 114 KB
- metadata.json 3.0 KB
- README.md 2.6 KB
- rules/_sections.md 2.4 KB
- rules/_template.md 670 B
- rules/comments-closing-brace-labels.md 3.5 KB
- rules/comments-empty-docblocks.md 3.8 KB
- rules/comments-narration.md 4.2 KB
- rules/comments-placeholder.md 4.0 KB
- rules/defensive-generic-catch.md 5.5 KB
- rules/defensive-impossible-null.md 5.3 KB
- rules/defensive-missing-real.md 6.1 KB
- rules/naming-generic-placeholders.md 3.9 KB
- rules/naming-over-descriptive.md 4.1 KB
- rules/naming-suffix-abuse.md 5.3 KB
- rules/naming-type-in-name.md 4.0 KB
- rules/over-eng-dependency-creep.md 4.3 KB
- rules/over-eng-premature-interface.md 5.0 KB
- rules/over-eng-single-method-class.md 4.8 KB
- rules/over-eng-useless-wrapper.md 4.6 KB
- rules/style-as-any-escape.md 5.0 KB
- rules/style-debug-artifacts.md 5.3 KB
- rules/style-hyper-consistent.md 5.0 KB
- rules/style-no-hack-scars.md 4.7 KB
- rules/style-trivial-boilerplate.md 5.9 KB
- rules/test-doesnt-throw.md 4.8 KB
- rules/test-mirror-implementation.md 5.0 KB
- rules/test-mock-everything.md 6.3 KB
- rules/test-snapshot-abuse.md 5.2 KB
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.
- 6d ago First seen · 246 lines · 110 tokens per session scan A d8cb86c721eb
code-slop is a skill published in the GitHub repository AsyrafHussin/agent-skills (72 stars, last pushed 9d ago), licensed MIT. It adds 110 tokens to every session and 3,012 once invoked, about $0.0006 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 skills, from other repositories
code-humanizer
Use when AI-written code needs structural cleanup or when implementing a change under a guard against AI coding slop — duplicated reimplementations of existing helpers, try-import fallbacks, broad exception swallowing, speculative abstraction layers, v2 copies, dead "for future use" code, narrating comments …
slop-review
Read-only slop review of prose, documentation, reports, agent output, commit messages or PR descriptions. Use when someone asks what is wrong with a draft, asks for an editorial or quality review, asks whether text is padded, vague, puffed up, unsourced or hollow, or asks whether writing "sounds like AI". Produces a…
slop-verify
Verification pass for citations, links, package names and vendor residue. Use when someone asks whether the sources in a document are real, asks to check DOIs, ISBNs, arXiv IDs or URLs, asks whether a cited source actually supports the claim attached to it, asks to check that imported packages exist, or asks to strip…
anti-slop-brain
Scaffold and operate Anti-Slop Brain, a source-cited Obsidian brain for detection and repair of AI slop in prose, code, documentation, and agent output, grounded in corpus evidence rather than authorship detection. Use when the user says "anti-slop-brain", "Anti-Slop Brain", "create a detection and repair of AI slop…
anti-slop
Router for the anti-slop toolkit. Use when someone asks to review, clean, de-slop, humanize, or quality-check prose, documentation, code, commit messages, PR descriptions, or agent output, or asks whether some writing "sounds like AI". Also use for verifying citations, DOIs, links and imported package names, for…
slop-code
Slop review and repair for source code, tests, configuration, generated documentation, README files, commit messages and pull request descriptions. Use when someone asks to review generated or agent-written code for quality, asks whether a diff is padded or ceremonial, asks about hallucinated or slopsquatted imports…