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/ScienceIsNeato/slop-mopWrote 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/scienceisneato/slop-mop/marketplace)<a href="https://agentmods.dev/plugins/scienceisneato/slop-mop/marketplace"><img src="https://agentmods.dev/badge/plugins/scienceisneato/slop-mop/marketplace/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/plugins/scienceisneato/slop-mop/marketplace"><img src="https://agentmods.dev/badge/plugins/scienceisneato/slop-mop/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
slopmop 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 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.
What it actually says
{
"name": "slopmop",
"owner": {
"name": "ScienceIsNeato",
"url": "https://github.com/ScienceIsNeato"
},
"description": "Slop-mop quality gates as a Claude skill — directed remediation for AI-assisted codebases.",
"metadata": {
"description": "Slop-mop quality gates as a Claude skill — directed remediation for AI-assisted codebases."
},
"plugins": [
{
"name": "slopmop",
"source": {
"source": "github",
"repo": "ScienceIsNeato/slop-mop"
},
"description": "Protocols for highly efficient and directed remediation of known issues — refit onboarding, the swab/scour/buff/sail loop, and barnacle friction reporting as a skill and slash commands.",
"category": "code-quality",
"keywords": [
"quality-gate",
"linting",
"testing",
"code-quality",
"ci-cd",
"ai",
"llm",
"vibe-coding",
"remediation",
"pre-pr"
],
"homepage": "https://github.com/ScienceIsNeato/slop-mop",
"license": "Apache-2.0",
"author": {
"name": "ScienceIsNeato",
"url": "https://github.com/ScienceIsNeato"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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 First seen · 41 lines scan A a594725a7323
slopmop marketplace is a plugin published in the GitHub repository ScienceIsNeato/slop-mop (13 stars, last pushed 22d 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-31.
Other plugins, from other repositories
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
adversarial-review
Cross-host adversarial review with material-only findings and mandatory over-engineering counterfactuals. Author-aware routing: Claude-authored work goes to Codex GPT-6 Astra high, then Grok 4.7 xhigh; Codex-authored work goes to Grok 4.7 xhigh, never back to Codex; then the Pi chain (DeepSeek V4 Flash, Kimi K3) and…
craft
Engineering standards for any code work on any stack — writing production code, slicing and reviewing PRs, authoring tests, running gates, merging, and running agent fleets.