Borrowing it
Nothing to install: this file belongs to jonathanmalkin/jules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonathanmalkin/jules/main/.claude/skills/stop-slop/SKILL.mdgit clone --depth 1 https://github.com/jonathanmalkin/julesWrote 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/jonathanmalkin/jules/stop-slop)<a href="https://agentmods.dev/skills/jonathanmalkin/jules/stop-slop"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/stop-slop.svg" alt="Measured on agentmods" 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.00066 | $0.01346 |
| Opus 5 | $0.00033 | $0.00673 |
| Sonnet 5 | $0.00013 | $0.00269 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
stop-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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stop Slop: Structural AI Pattern Audit
Eliminate structural AI writing patterns from prose. This skill focuses on paragraph-level and structural tells that survive word-level editing. Voice-Profile.md handles banned words/phrases. This handles the architecture of the writing.
When to Use
- Content pipeline output (articles, Reddit posts, X threads) before publishing
- As part of
/write-articleStage 5 review panel - In content agent
humanizemode as Pass 3 (structural audit) - Manual invocation via
/stop-slopon any draft
Do NOT run on: Jules conversational output, internal docs, code comments, quick replies.
Core Rules
-
Break formulaic structures. No binary contrasts ("Not X. Y."), negative listings, dramatic fragmentation, rhetorical setups. See
references/structures.md. -
Kill false agency. Inanimate things don't perform human actions. "The complaint becomes a fix" = no. "The team fixed it" = yes. Name the human actor.
-
Use active voice. Every sentence needs a subject doing something. No passive constructions hiding the actor.
-
Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing.
-
Put the reader in the room. No narrator-from-a-distance. "You" beats "People." Specifics beat abstractions.
-
Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes. No staccato fragmentation stacking.
-
Trust readers. State facts directly. Skip softening, justification, hand-holding.
-
Cut quotables. If it sounds like a pull-quote, rewrite it.
-
No formulaic article structure. Don't default to: intro hook, context, 3-5 body sections, takeaway, CTA. Vary. No "Final thoughts" or "Key takeaways" headers. No rhetorical questions as section transitions.
What ships with it
3 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.
- 6d ago First seen · 112 lines · 66 tokens per session scan A 6812667e9b39
stop-slop is a skill published in the GitHub repository jonathanmalkin/jules (65 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 1,346 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…