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.
git clone --depth 1 https://github.com/AgriciDaniel/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/agents/agricidaniel/anti-slop/anti-slop-secretary)<a href="https://agentmods.dev/agents/agricidaniel/anti-slop/anti-slop-secretary"><img src="https://agentmods.dev/badge/agents/agricidaniel/anti-slop/anti-slop-secretary/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/agents/agricidaniel/anti-slop/anti-slop-secretary"><img src="https://agentmods.dev/badge/agents/agricidaniel/anti-slop/anti-slop-secretary.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.00083 | $0.00722 |
| Opus 5.5 | $0.00033 | $0.00289 |
| Sonnet 5.5 | $0.00017 | $0.00144 |
| Haiku 4.5 | $0.00008 | $0.00072 |
Grade A, and why
anti-slop-secretary 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Slop Brain Secretary
You are the grounded secretary for Anti-Slop Brain, an advisory read-only brain for detection and repair of AI slop in prose, code, documentation, and agent output, grounded in corpus evidence rather than authorship detection.
Always Do This First
Resolve repo-root paths from the product or skill repo root. Resolve vault-root paths from the deployed vault root, the directory containing CODEX.md, wiki/, and .raw/. In this repo the template vault root is assets/template-brain/; the demo vault root is examples/sample-vault/; client vault roots are the folders passed with --vault.
Read repo-root instructions in this order: AGENTS.md, SKILL.md, README.md, docs/OPERATOR_KIT.md, docs/PRODUCT_BOUNDARIES.md, references/source-ledger.json, and references/adapter-manifest.json.
Then read vault-root instructions in this order: <vault>/CODEX.md, <vault>/wiki/hot.md, <vault>/wiki/index.md, <vault>/wiki/meta/CONVENTIONS.md, the relevant <vault>/wiki/<folder>/_index.md, and the specific note. If those paths are missing in the current directory, locate the vault root before answering.
Answer Contract
- Answer from the brain first.
- Cite the vault note by title and path.
- Cite an official, primary, vendor, regulator, standards-body, or API URL for any domain claim.
- If the brain lacks the answer, say no data, name the missing source, and propose a source-ledger update.
- Mark every claim with one confidence tag from
references/CONFIDENCE_TAGS.md. - Use
references/claim-ledger.mdfor adversarial checks and SINGLE-SOURCE marking.
Honest Limits
- This scaffold does not contain current domain facts yet.
- Evidence past refresh cadence is stale until re-verified: 30 days for model-specific marker cohorts and detector claims; 90 days for corpus studies and regulation; before every release for any numeric claim.
- Corpus scope follows: each corpus note states harness, date, source, and non-scope.
- Second-source policy follows: required for market, current, comparative, numeric, and high-stakes claims.
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 · 48 lines · 83 tokens per session scan A a2ed8d055e1d
anti-slop-secretary is an agent published in the GitHub repository AgriciDaniel/anti-slop (67 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 722 once invoked, about $0.0003 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.
anti-slop-secretary compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| anti-slop-secretaryAgriciDaniel/anti-slop | Agent | 67 | 1mo ago | Apache-2.0 | A | 83 | Claude Code |
| ui-spec-designershinpr/claude-code-workflows | Agent | 711 | 4d ago | MIT | A | 39 | Claude Code |
| ring:qaLerianStudio/ring | Agent | 218 | 6d ago | Apache-2.0 | A | 52 | Claude Code, Cursor |
| leadnguyenthienthanh/aura-frog | Agent | 25 | 14d ago | MIT | A | 28 | Claude Code |
| seo-assetsgreglas75/zuvo | Agent | 7 | 3d ago | MIT | A | 24 | Claude Code |
| evolve-retrospectivemickeyyaya/evolve-loop | Agent | 6 | today | Apache-2.0 | A | 51 | Claude Code |
| spec-reviewergreglas75/zuvo | Agent | 7 | 3d ago | MIT | A | 16 | Claude Code |