Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/roedyrustam/vibes-plugnpx agentmods add rules/roedyrustam/vibes-plug/vibes-plug-anti-slopWrote 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/rules/roedyrustam/vibes-plug/vibes-plug-anti-slop)<a href="https://agentmods.dev/rules/roedyrustam/vibes-plug/vibes-plug-anti-slop"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/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/rules/roedyrustam/vibes-plug/vibes-plug-anti-slop"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/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.00670 | $0.00670 |
| Opus 5.5 | $0.00268 | $0.00268 |
| Sonnet 5.5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
vibes-plug-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 2d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sovereign Anti-AI Slop Directive (Cursor Enforcement)
Pillar 1: Conversational Slop Eradication
- Deliver code directly. Never apologize robotically, never repeat user prompts verbatim, zero trailing cheerleading.
- Provide succinct architectural rationale (WHY) rather than narrative descriptions of mechanics.
Pillar 2: Placeholder & Truncation Elimination (Absolute Invariant)
- NEVER output lazy placeholder comments like:
// TODO: Implement later// ... rest of code remains unchanged .../* Add other fields here */
- Any code file produced MUST be 100% complete, fully implemented, syntactically valid, and working on the first try.
- Fake mock arrays and in-memory stubs are strictly forbidden in production endpoints.
Pillar 3: Speculative Over-Engineering (Hyper-YAGNI)
- Ban premature abstraction layers, unnecessary factories, and redundant DTO wrappers.
- Rely on static types and strict schema contracts (
TypeSpec,OpenAPI 3.1,Zod,Pydantic).
Pillar 4: Syntax Narration vs Architecture Rationale
- Comments must only explain non-obvious business invariants, architectural trade-offs, or mathematical bounds.
- Delete dead, commented-out code permanently.
Pillar 5: Hallucination & AI Smells
- Ban phantom imports and fabricated library methods.
- Ban silent error suppression (
catch (e) {}is strictly prohibited). Always log structured errors with context (Pino/Sentry).
Pillar 6: Documentation Sanitation
- Technical specs must contain concrete PostgreSQL DDL schemas, JSON request/response contracts, and numeric NFR budgets. Zero vague corporate buzzwords.
Pillar 7: Professional UI Craftsmanship (Linear/Stripe-Caliber)
- Zero generic AI UI tropes: No purple-indigo neon gradients, no blurred neon glow orbs, no pill button addiction (
rounded-fullon rectangular buttons is banned). - 5-State Interactive Contract: Every button, input, and interactive component must define 5 distinct visual states:
defaulthoverfocus-visible(keyboard accessibility focus ring)active(pressed down state)disabled(clear contrast reduction and cursor-not-allowed)
- Tabular Numerals: Always apply
tabular-numson monetary figures, counters, tables, and metrics to prevent layout shifts. - Borders & Radius: Crisp
1pxsubtle borders (border-border/50orring-1 ring-border) with intentional radius scales (e.g.,rounded-lg).
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.
- 2d ago First seen · 52 lines · 670 tokens per session scan A f07661555eef
vibes-plug-anti-slop is a cursor rule published in the GitHub repository roedyrustam/vibes-plug (112 stars, last pushed today), licensed MIT. It adds 670 tokens to every session, about $0.0027 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-10-21.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .