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 d-oit/rust-2026-template --skill anti-ai-slopgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/anti-ai-slop)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/anti-ai-slop"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/anti-ai-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/d-oit/rust-2026-template/anti-ai-slop"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/anti-ai-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.00112 | $0.01713 |
| Opus 5.5 | $0.00045 | $0.00685 |
| Sonnet 5.5 | $0.00022 | $0.00343 |
| Haiku 4.5 | $0.00011 | $0.00171 |
Grade A, and why
anti-ai-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 1mo 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-AI-Slop Skill — Rust Edition
How to Use
- Audit mode — Share code. Run through checklists below. Name every pattern.
- Creation mode — Read "What to do instead" first, then write code avoiding patterns.
- Spot-fix mode — Point to one element. Diagnose it, rewrite it, explain the fix.
Always name the problem before fixing it.
Part 1 — Code Structure Anti-Patterns
| Pattern | What it looks like | Why it's slop |
|---|---|---|
| Wrapper struct for no reason | struct MyError(String) with no extra behavior |
Just use anyhow::Error or the inner type directly |
| Over-engineered trait hierarchy | trait Processor<T: Handler<U>> for one impl |
One trait, one impl = delete the trait |
mod utils |
mod utils { pub fn helper(...) } |
No concept. Scatter into real modules |
mod common |
Grab-bag module used by everything | Symptom of no domain model |
| Phantom generics | struct Foo<T> { _marker: PhantomData<T> } with no bounds |
If T does nothing, remove the generic |
| Re-export sprawl | pub use inner::* chains 3 levels deep |
Forces users to trace invisible paths |
| Builder for 2 fields | FooBuilder::new().name(x).value(y).build() |
Just use Foo { name: x, value: y } |
What to Do Instead
- Model the domain. Name types after what they represent, not their role in the code.
- Flat module tree. One level deep is almost always enough.
- Direct construction. Struct literals over builders unless >5 optional fields or invariants.
- Concrete before abstract. Start with one function. Extract trait only when you have 2+ impls.
Part 2 — Error Handling Anti-Patterns
| Pattern | What it looks like | Why it's slop |
|---|---|---|
.unwrap() in library code |
value.parse().unwrap() |
Panics in calling code without context |
| `.expect("should not happen") | everywhere | If it can happen, handle it. If not, prove it. |
Box<dyn Error> in all signatures |
fn run() -> Result<(), Box<dyn Error>> |
Erases error type, forces dynamic dispatch |
| `map_err(|_| "failed") | Error message that says nothing | Include the input, the operation, what failed |
match err { _ => return Err(...) } |
Manual error forwarding | Use ? operator |
| Custom error type per function | ParseConfigError, LoadConfigError, ReadConfigError |
One ConfigError with variants |
What ships with it
1 file 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.
- 1mo ago Changed · -7 lines 76f529af130e
- 2mo ago First seen · 144 lines · 112 tokens per session scan A e5edd898e42d
anti-ai-slop is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session and 1,713 once invoked, about $0.0004 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-31.
Other skills, from other repositories
m15-anti-pattern
Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production…
unsafe-checker
A review guide for unsafe Rust code and foreign-function interfaces, which let Rust call code written in languages such as C. It covers raw pointers, memory layout, `extern` functions, safety comments, and undefined behavior.
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
writing-rust
Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.
architectural_review
Review Rust code for advanced architectural patterns — capability mixins, typed commands, concurrency model choice, smart pointer/interior mutability selection, error-handling architecture, and memory layout. Use when the user asks to review system architecture, suggest broad design improvements, or evaluate trait…
hexagonal_review
Review a Rust codebase for hexagonal architecture compliance — dependency direction, port shape, adapter grouping, error boundaries, feature-flag placement, and testability. Use when the user asks to review architecture, audit layering, check ports-and-adapters discipline, or evaluate whether a Rust project's…