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 skills add roedyrustam/vibes-plug --skill anti-slopgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/anti-slop)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/anti-slop"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/anti-slop/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/roedyrustam/vibes-plug/anti-slop"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/anti-slop.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.00113 | $0.09459 |
| Opus 5.5 | $0.00045 | $0.03784 |
| Sonnet 5.5 | $0.00023 | $0.01892 |
| Haiku 4.5 | $0.00011 | $0.00946 |
Grade A, and why
anti-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 5d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sovereign Anti-AI Slop & Craftsmanship Engine (2026 Unified Edition)
English
Executive Directive & Trigger Conditions
The Sovereign Anti-Slop Directive is the uncompromising zero-tolerance standard governing all AI agent actions across the vibes-plug swarm. AI slop degrades developer trust, burns context tokens, bloats codebases, and introduces catastrophic production defects.
Anti-slop is a filter, not a style guide: it prescribes no fixed colors, fonts, or layouts—your creative direction remains yours. Removing slop clears away generic AI habits, while the Liveliness Toolkit ensures the final product is vivid, authentic, and deliberate rather than sterile.
Universal Trigger Conditions:
- Every Code Generation & Modification: Every function, component, or file created or modified by any agent.
- Frontend & UI Work: Design systems, page layouts, components, cards, dashboards, and responsive styling.
- Copywriting & Prose: Headlines, CTAs, product copy, documentation, commit messages, and PR summaries.
- Code Comments: Documentation comments, inline annotations, and docstrings.
- Automated Quality Gates & PR Audits: Code reviews (
coderabbit), TDD loops (autonomous-tdd-debugger), and production release hardening (production-ready-hardener).
Two Usage Modes Protocol
On every anti-slop activation, resolve the operational mode in this strict priority:
- Explicit Session Instruction: User specifies
duringorafterin the prompt. Announce once:antislop active: <mode> (session override). - Global Preference: Read
%APPDATA%\antislop\settings.json(Windows) or~/.config/antislop/settings.json(macOS/Linux). - Default Fallback: Mode 1 (DURING) for new features/code generation; Mode 2 (AFTER) when auditing existing projects.
Mode 1: DURING (Active Real-Time Prevention)
- Follow all 38 rules actively while generating code, copy, and UI.
- Prevents slop from being written in the first place.
- Conclude the task with the Mandatory Delivery Gate report.
What ships with it
2 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.
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.
- 5d ago Changed · +3 lines fff6b5866d4d
- 6d ago Changed · +1 lines 213b01c86ea7
- 7d ago Changed d4680959b78e
- 9d ago Changed cac997739454
- 18d ago Changed · -187 lines · +24 tokens per session 7a1b8fcb7e7e
- 21d ago Changed · +178 lines 82ab37b6ab8e
- 23d ago Changed · +141 lines · +9 tokens per session a72445d742a3
- 24d ago Changed 23ae6d305c4b
- 26d ago Changed · +220 lines · +70 tokens per session 7ab77efe12f2
- 28d ago First seen · 140 lines · 10 tokens per session scan A 98fc17b62003
anti-slop is a skill published in the GitHub repository roedyrustam/vibes-plug (114 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 9,459 once invoked, about $0.0005 per session on Opus 5.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-09-12.
Other skills, from other repositories
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
pr
A writing guide for creating pull request descriptions, which explain a proposed code change to reviewers. It uses sections for the summary, evidence, merge risk, and the likely area affected by the change.
code-review
A code-review skill that compares changes from a chosen commit, branch, tag, or merge-base against the repository’s coding standards and the related issue or specification.
improve-codebase-architecture
A skill that scans a codebase for places where restructuring could make future changes and testing easier, then produces an HTML report for selected improvements.
ai-architect-review
Review the architecture of a system that calls a language model. Use when adding an agent loop, a retrieval path, a tool surface, or an MCP server to a codebase; when a system that worked in a demo is being prepared for production; or when asked to audit, review, or plan AI/agent architecture. Checks the four…
github-code-review
Comprehensive GitHub pull-request code review with multi-agent coordination. Use when reviewing a PR or diff, auditing changes for correctness/security/style before merge, or generating actionable inline review comments.