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/plugins/agricidaniel/anti-slop/marketplace)<a href="https://agentmods.dev/plugins/agricidaniel/anti-slop/marketplace"><img src="https://agentmods.dev/badge/plugins/agricidaniel/anti-slop/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
anti-slop marketplace 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 7d 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.
What it actually says
{
"name": "anti-slop",
"description": "Find and repair substance defects in AI-assisted prose, code, documentation, and agent output. Reports defects, never authorship.",
"owner": {
"name": "Daniel Agrici",
"url": "https://github.com/AgriciDaniel"
},
"plugins": [
{
"name": "anti-slop",
"displayName": "Anti-Slop",
"description": "Detect and repair AI slop in prose, code, documentation, commits and agent output. Reports defects, never authorship. Runs deterministic scanners for vendor residue, placeholders, citations and packages, then structural procedures (deletion, inversion, stranger, attribution, load-bearing) that each emit a verifiable artifact. Stylistic markers are evidence-tiered and route to structural tests instead of failing on their own.",
"author": {
"name": "Daniel Agrici",
"url": "https://github.com/AgriciDaniel"
},
"category": "writing",
"version": "0.1.0",
"homepage": "https://github.com/AgriciDaniel/anti-slop",
"keywords": [
"anti-slop",
"ai-slop",
"writing-quality",
"code-review",
"citations",
"provenance"
],
"source": {
"source": "git-subdir",
"url": "https://github.com/AgriciDaniel/anti-slop.git",
"path": "anti-slop-plugin",
"ref": "main"
}
}
]
}
The plugins it lists here
This marketplace lists 2 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 7d ago First seen · 37 lines scan A 166e5beaf1a2
anti-slop marketplace is a plugin published in the GitHub repository AgriciDaniel/anti-slop (45 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
procoder
A harness that gives AI coders the tools and skills to work like a senior developer. All nine domains shipped: security, best practices, maintainability, performance, documentation, clean code, CI/CD, DevOps, GitOps — plus the code index. Hooks hand the agent results; the agent stays in control.
argot
A guardrail that flags code foreign to a repo's own patterns — learned from git history. Bundles the argot-setup, argot-refresh, argot-check, argot-review-pr, argot-setup-ci, argot-write-rule, and argot-suggest-rules skills, the argot MCP server, and an opt-in, non-blocking pre-write guardrail hook.
skill-reviewer
Use when reviewing a Claude Code skill, auditing skill quality before publish, or asking "is this skill any good?". Produces structured reports with file:line citations, severity-rated findings cards, and an optional second-opinion pass. Lens variants: full (default), safety, discoverability, architecture…
dev-workflow
Spec-driven workflow with two independent cross-model review gates, an append-only hardening ledger with an escalation ladder, and repo-enforced quality. Requires the superpowers plugin.
hi-vibe
Vibe-coding seatbelt for Claude Code — doc automation (CLAUDE.md/MODULE.md/handover/CHANGELOG) + AI discipline (root-cause first, no unfounded claims) + machine enforcement (ruff/eslint/import cycles).
guardsman
Right-sized code, verified before it ships. Risk-tiered engineering judgment for AI coding agents: convention detection, blast-radius tiers, mandatory verification, and a scannable logbook for deliberate shortcuts.