anti-slop vs stop-that-shit
The two are close in size: 1.0k stars for anti-slop, 1.6k for stop-that-shit.
anti-slop leads on model freedom and setup ease. stop-that-shit does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
A rule-based filter with a mandatory PASS/FAIL Delivery Gate and liveliness toolkit focused on removing generic AI-generated UI and copy without prescribing visual style.
- Stars
- 1.0k
- Tracked growth
- +131.3%
- Maturity
- ●●●●●
- Last commit
- 18h ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free to use; runs locally or via your agent/API
Implements executable, evidence-backed Guards and Skills that intercept unrequested hashes, dependency/subagent launches and scope creep across multiple agent hosts, turning policy statements into machine-enforceable checks.
- Stars
- 1.6k
- Tracked growth
- not tracked long enough
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free, local install; uses the host agent's model access (may require provider subscriptions).
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | anti-slop | stop-that-shit |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff + related files | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Hard gates + report | ●●●●● Armed / observing gating |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Configurable skills & dials | ●●●●● Command flags & policies |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Any agent / BYOK | ●●●●● Multiple specific providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command / npx | ●●●●● Install + restart |
Which one to pick
Pick anti-slop if…
Easy setup — one-command picker or a single-file install drops a portable, non-prescriptive filter into many coding agents so you can stop AI 'slop' fast.
- Model freedom: Any agent / BYOK (5/5 against 3/5)
- Setup ease: One-command / npx (5/5 against 3/5)
Pick stop-that-shit if…
Privacy-first — a local-first plugin that enforces task-boundary guardrails across Codex, Claude Code, OpenCode and Hermes Agent CLI without relying on a centralized service.
What people want from each one
lennney/stop-that-shit
Questions people ask
Is anti-slop better than stop-that-shit?
anti-slop leads on model freedom and setup ease. stop-that-shit does not take any axis by a clear margin. anti-slop is worth picking when easy setup — one-command picker or a single-file install drops a portable, non-prescriptive filter into many coding agents so you can stop AI 'slop' fast.
Which of anti-slop and stop-that-shit keeps my code private?
anti-slop: Self-hostable (4/5). stop-that-shit: Self-hostable (4/5).
What does each one cost to run?
anti-slop: Free to use; runs locally or via your agent/API. stop-that-shit: Free, local install; uses the host agent's model access (may require provider subscriptions)..
Full profiles: miqdadbadjuber/anti-slop and lennney/stop-that-shit. Everything else in Security & guardrails.