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 aragaobruno/toolbelt --skill ai-slop-detectorgit clone --depth 1 https://github.com/aragaobruno/toolbeltWrote 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/aragaobruno/toolbelt/ai-slop-detector)<a href="https://agentmods.dev/skills/aragaobruno/toolbelt/ai-slop-detector"><img src="https://agentmods.dev/badge/skills/aragaobruno/toolbelt/ai-slop-detector/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/aragaobruno/toolbelt/ai-slop-detector"><img src="https://agentmods.dev/badge/skills/aragaobruno/toolbelt/ai-slop-detector.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.00039 | $0.00570 |
| Opus 5 | $0.00019 | $0.00285 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
ai-slop-detector 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧠 ai-slop-detector
Overview
AI-generated text is often bloated with repetitive words, formal clichés ("throat-clearing" intros), and structural patterns that make it instantly recognizable as machine-generated. The ai-slop-detector audits your prose, documents, and code comments, highlights these patterns, and sanitizes them to produce clean, natural, and human-like writing.
Quick Start
To scan a markdown file for AI jargon:
node skills/context/ai-slop-detector/scripts/detector.js check README.md
To automatically rewrite a document to remove AI slop:
export GEMINI_API_KEY="your-gemini-key"
node skills/context/ai-slop-detector/scripts/detector.js clean draft.md --output final.md
Utility Scripts
detector.js (CLI)
A Node.js tool to detect and clean AI writing patterns.
Subcommand: check
Scans the target file against a set of heuristic rules representing common AI writing flaws.
- Arguments:
<file_path> - Example:
node detector.js check blog_draft.md
Subcommand: clean
Invokes the Gemini API to intelligently rewrite the file, stripping all slop while preserving the original intent and technical accuracy.
- Arguments:
<file_path> --output <output_file_path> - Example:
node detector.js clean raw_draft.md --output clean_prose.md
Common Pitfalls (Slop Dictionary)
Below are the primary patterns targeted by this skill:
- Introductory Clichés ("Throat-clearing"):
- Avoid: "In today's fast-paced digital landscape...", "It is important to note that...", "In this article, we will delve into..."
- Write: Direct, punchy openers.
- Robotic Transitions:
- Avoid: "Furthermore", "Moreover", "Additionally", "In summary", "Ultimately", "It is testament to..."
- Write: Standard, conversational transitions.
- Vague AI-isms:
- Avoid: "Delve", "Tapestry", "Bespoke", "Revolutionize", "Beacon", "Pivotal".
- Write: "Explore", "Structure", "Custom", "Improve", "Key".
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.
- 11d ago First seen · 56 lines · 39 tokens per session scan A ad8dc0a3da08
ai-slop-detector is a skill published in the GitHub repository aragaobruno/toolbelt (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 570 once invoked, about $0.0002 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
ai-project-starter
Use when the user wants to prepare project-specific context engineering documents, AI coding agent instruction files, project starter Markdown files, vibe coding guardrails, PRD/TDD/architecture/security/testing docs, AGENTS.md/CLAUDE.md/Cursor/Windsurf/Continue/Copilot context files, or a complete AI-coding-ready…
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
repo-harness
Route explicit repo-harness setup, planning, execution, verification, and handoff actions through deterministic repository state.
report
Investigate bugs comprehensively — cascade through trace, capture browser evidence, extract observability data, and prepare or explicitly create a GitHub issue with grounded findings.