Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AgriciDaniel/anti-slop/plugin install 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/skills/agricidaniel/anti-slop/slop-rewrite)<a href="https://agentmods.dev/skills/agricidaniel/anti-slop/slop-rewrite"><img src="https://agentmods.dev/badge/skills/agricidaniel/anti-slop/slop-rewrite/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/agricidaniel/anti-slop/slop-rewrite"><img src="https://agentmods.dev/badge/skills/agricidaniel/anti-slop/slop-rewrite.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.00174 | $0.02062 |
| Opus 5 | $0.00087 | $0.01031 |
| Sonnet 5 | $0.00035 | $0.00412 |
| Haiku 4.5 | $0.00017 | $0.00206 |
Grade A, and why
slop-rewrite 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 11d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slop rewrite
The firewall
These four rules bind this skill and hold even when the user asks for the opposite.
- Never emit an authorship verdict. Report defects, not origin. Never state or imply that the original was written by a human, by AI, or by a named model.
- Never hard-fail on a stylistic marker alone. A marker is a routing hint. Its only legitimate output is "run a structural test on this span".
- Severity is impact. Confidence is certainty. Two axes. Never merge them, never trade one against the other.
- Never let the model gate its own rewrite. The deterministic scanners
re-run after any fix and their exit codes decide, not your judgment. A
PostToolUse hook on this skill re-runs
scan_residue.pyandscan_placeholders.pyafter every write. If the hook cannot run, you run them yourself and quote the exit codes.
Standing instructions
Consume findings. Never re-derive them. This skill's input is a findings report with IDs, quotes, severities and confidences. Fix what is listed. If you believe something else is wrong, say so in the closing report as an unactioned observation; do not silently fix it, and do not run structural tests here. The separation exists because a model that judges and then repairs in one pass scores its own work, and self-gating produces a measured rubber-stamp regime where acceptance rises while correctness falls (Song, Cai and Zhao, arXiv 2606.28438, 2026-06-26).
If no findings report exists, stop and get one. Run slop-review first, or
ask the user for their defect list. Rewriting without a report is exactly the
failure mode this plugin exists to prevent.
Never invent a fact. The rewrite must not contain any fact, name, number, date, quote or citation that is not in the source text or supplied by the user. Swapping a vague claim for a specific one is allowed only when the specific comes from the source. If a sentence needs real-world detail to work, ask for it, or write the plain version without it, or cut the sentence. An unsupported claim gets cut, not decorated.
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.
- 11d ago First seen · 168 lines · 174 tokens per session scan A c0c40d6f8392
slop-rewrite is a skill published in the GitHub repository AgriciDaniel/anti-slop (48 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 174 tokens to every session and 2,062 once invoked, about $0.0009 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
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:mapping-streaming-events
Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…