What is slop-rewrite?

A repair process for an existing review report that lists problems in a draft, document, report, or agent response. It fixes only the listed issues, including padding, vendor residue, and placeholder text.

Use it after a slop review to tighten writing, remove filler, and clean up placeholders or leftover vendor wording. It requires a findings report as input.

It prevents a rewrite from changing unrelated content or silently addressing problems that were not reviewed. Automated scans check the result after edits.

slop-rewrite — Skill for Claude Code by AgriciDaniel/anti-slop

Install

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.

Claude Code

/plugin marketplace add AgriciDaniel/anti-slop

Claude Code

/plugin install anti-slop

Made for: Claude Code.

Or install anti-slop, the plugin that ships this one along with the rest of its 5 skills, 2 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/agricidaniel/anti-slop/slop-rewrite/github.svg)](https://agentmods.dev/skills/agricidaniel/anti-slop/slop-rewrite)

Your own site

<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.

Your own site · 80×15

<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>

Per session 174 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,062 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00070	$0.00825
Sonnet 5.5	$0.00035	$0.00412
Haiku 4.5	$0.00017	$0.00206

Measured 2mo ago against content hash c0c40d6f8392, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

anti-slop-plugin/skills/slop-rewrite/SKILL.md · 168 lines

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.py and scan_placeholders.py after 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.

Read the full file on GitHub · 168 lines

Changes

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.

2mo ago First seen · 168 lines · 174 tokens per session scan A c0c40d6f8392

Subscribe to this mod's changes

slop-rewrite is a skill published in the GitHub repository AgriciDaniel/anti-slop (67 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 174 tokens to every session and 2,062 once invoked, about $0.0007 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-08-30.

Claude Code Writing and docs agent-skills ai-slop citation-verification code-quality writing-quality

slop-rewrite next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slop-rewriteAgriciDaniel/anti-slop	Skill	67	1mo ago	Apache-2.0	A	174	Claude Code
code-slopAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	110	Claude Code, Codex
git-workflowAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	59	Claude Code, Codex
laravel-inertia-reactAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	59	Claude Code, Codex
laravel-owasp-securityAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	87	Claude Code
seo-best-practicesAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	78	Claude Code
state-managementAsyrafHussin/agent-skills	Skill	102	2mo ago	MIT	A	47	Claude Code, Codex