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 mattmre/EVOKORE-MCP-PUBLIC --skill anti-slopgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/anti-slop)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/anti-slop"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/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/mattmre/evokore-mcp-public/anti-slop"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/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.00056 | $0.01258 |
| Opus 5 | $0.00028 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
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 12d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Slop Skill
Use this skill when you want to audit a recent stretch of tool calls (your own, an agent's, or a session replay log) for wasteful patterns that burn context and time without producing work. The goal is to surface concrete violations, not give vague style advice.
This skill is paired with the anti-slop PostToolUse hook, which
emits the same warnings to stderr in real time when
EVOKORE_ANTISLOP_HOOK=true (or via a protection profile that
enables it). Both surfaces share the same definitions of "slop"
below.
Trigger
Apply this skill when:
- About to start a new pass and want to check whether the previous segment was wasteful.
- Reviewing a long autonomous-loop transcript before merging or summarizing.
- Triaging why a session is slow or feels confused.
- Operating with
EVOKORE_ANTISLOP_HOOK=trueand you see a stderr advisory and want to understand the underlying rule.
Do not apply it as a blocking gate. The hook is warning-only by design, and so is the skill.
The patterns
Pattern A — Re-read after edit
Reading a file immediately after
Edit/Write/MultiEditsucceeded on it.
The Edit/Write tools error if the change failed; on a clean response
the file already matches your new_string and the harness tracks
file state for you. Re-reading just to "verify" burns context with
no new information.
What to do instead: trust the edit. If you genuinely need to see a different region you didn't pre-load, read only the new offset/limit range. Do not re-read the whole file.
Pattern B — Repeated reads of the same path
Three or more consecutive
Readcalls on the same path with no Edit/Write between them.
This usually means you're looking for something you already saw and have lost track of, or you're paging through the file inefficiently. Either way, the third read costs you context that the first two should have answered.
What to do instead: scroll back in your own context to find the
prior read. If you need a different range, jump there directly with
offset/limit instead of re-reading from line 1.
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.
- 12d ago First seen · 137 lines · 56 tokens per session scan A a491770319b7
anti-slop is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,258 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-31.
Other skills, from other repositories
adversarial-thinking
A five-part check that challenges a proposed plan before it is built or used. It examines unusual inputs, security risks, performance under larger workloads, unavailable dependencies, and contradictions within the plan.
peak-end-rule
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
critique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).