Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

anti-slop

anti-slop

Skills that stop AI coding agents from shipping garbage.

Same prompt → smaller diffs. Less fake architecture. PRs you’d actually merge.


npx skills add iCodeCraft/anti-slop

Cursor · Claude Code · Codex · 70+ agents · Agent Skills · MIT


Same prompt. Half the slop.

Empty folder. Same model. One prompt:

Create a production-ready FastAPI backend for authentication and a personal todo list.
I need register, login, create/list/toggle todos. In-memory storage is fine.

Without anti-slop: 13 files, 433 lines   With anti-slop: 5 files, 222 lines

13 files · 433 lines  →  5 files · 222 lines   ·   −62% files · −49% lines

JWT auth and todos either way. anti-slop cuts the architecture cosplay — routers, schemas, dependencies, config theater → main + auth + store.

Reproduce the A/B

Prompt, logging table (model + date), and notes: examples/README.md.

Published delta (one measured empty-folder run): 13 → 5 files, 433 → 222 lines. Re-runs vary by model; log yours when you reproduce.


Why it exists

Agents overbuild. You correct the same junk every chat.

Extra files. Strategy patterns for one use. Comments that restate the code. Drive-by refactors. Clean Architecture on a todo app.

anti-slop writes the rules down once. The agent loads them when the task matches — not as a pasted paragraph you repeat forever.


Three skills. One job each.

Skill Does
/kill-slop kill-slop Minimal diffs. No drive-bys, junk comments, unrequested files/deps, or architecture cosplay.
/security-review security-review Diff-scoped findings: authz, injection, secrets, SSRF, unsafe defaults.
/pr-hygiene pr-hygiene Tight scope, honest PR body, no leftover debug.

New session → skills load when relevant, or type the command.

What kill-slop forbids
  • New files that could live in an existing one
  • Dependencies you didn’t ask for
  • Unrelated refactors
  • Obvious comments (// return result)
  • Abstractions for a single use
  • Invented domain/ / application/ / infrastructure/ trees
  • Fishing outside the workspace for “inspiration”

Full playbook: skills/kill-slop/SKILL.md.

What security-review catches

Diff-scoped — not a whole-repo audit. Example: examples/security-review.

// Looks fine. Ships a data leak.
app.get("/api/invoices/:id", async (req, res) => {
  const invoice = await db.invoices.findById(req.params.id);
  if (!invoice) return res.status(404).end();
  return res.json(invoice); // no ownership check
});

/security-review flags missing authorization — client-supplied id ≠ proof of access.


Install

npx skills add iCodeCraft/anti-slop
# pin an agent
npx skills add iCodeCraft/anti-slop -a cursor -y
npx skills add iCodeCraft/anti-slop -a claude-code -y

# every project on this machine
npx skills add iCodeCraft/anti-slop -g -y

# manage
npx skills list
npx skills remove kill-slop
Where skills land
Tool Project Global
Cursor .agents/skills/ ~/.cursor/skills/
Claude Code .claude/skills/ ~/.claude/skills/
Codex / others .agents/skills/ under ~/

Portable via the skills CLI — no Cursor-only lock-in.


Contributing · keep skills focused · MUST/NEVER over essays · CONTRIBUTING.md

About

Drop-in skills that stop AI coding agents from shipping garbage — kill-slop, security-review, PR hygiene

Topics

Resources

Contributing

Stars

Watchers

Forks

Contributors

Languages