A coding-agent skill that directs repository cleanup and quality work through slop-mop commands. Slop-mop is a command-line tool with one-time onboarding and ongoing maintenance checks.

Use it when setting up slop-mop, maintaining a repository, or when you would otherwise reach for tools such as tests, type checks, formatting, or GitHub commands.

It gives agents an established sequence for setup, cleanup, checks, pull requests, and reporting tool-related friction.

slopmop — Skill for Claude Code by ScienceIsNeato

Install

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.

Any agent

npx skills add ScienceIsNeato/slop-mop --skill slopmop

Clone the repo

git clone --depth 1 https://github.com/ScienceIsNeato/slop-mop

Made for: Claude Code.

Or install slopmop, the plugin that ships this one along with the rest of its 1 skill, 8 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/scienceisneato/slop-mop/slopmop/github.svg)](https://agentmods.dev/skills/scienceisneato/slop-mop/slopmop)

Your own site

<a href="https://agentmods.dev/skills/scienceisneato/slop-mop/slopmop"><img src="https://agentmods.dev/badge/skills/scienceisneato/slop-mop/slopmop/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/scienceisneato/slop-mop/slopmop"><img src="https://agentmods.dev/badge/skills/scienceisneato/slop-mop/slopmop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 186 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,598 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00186	$0.01598
Opus 5	$0.00093	$0.00799
Sonnet 5	$0.00037	$0.00320
Haiku 4.5	$0.00019	$0.00160

Measured 9d ago against content hash 64907a56a144, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

slopmop 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 9d 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.

skills/slopmop/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slop-mop skill

Filing slop-mop friction? Use /sm-barnacle or sm barnacle file — never gh issue create directly. The barnacle CLI auto-applies the correct labels and targets the right repo regardless of where you are.

Slop-mop (sm) has two primary modes: refit (one-time onboarding) and maintenance (steady-state development). Refit remediates all existing slop and installs permanent guards; the swab/scour/buff loop then keeps the repo clean as you work.

Setting up slop-mop in a repo (the install handoff)

When the user says "install slop-mop", "set up slop-mop in this repo", or similar, do not improvise ad-hoc setup. It is an ordered handoff — each step is a real CLI surface (sm -h lists them). Run them in order, skipping any that are already done:

CLI present? If sm is "command not found", install the utility: pipx install slopmop[all].
Repo-local agent instructions? Install them so every agent in this repo follows the rails: sm agent install (add --target copilot|cursor|claude as needed).
Config? If there's no .sb_config.json, generate one tuned to the detected stack: sm init --non-interactive.
Onboard the existing code: sm refit --start → sm refit --iterate → sm refit --finish, then enter the maintenance loop.

"Install slop-mop in the repo" means all of the above, not just step 1. If you are unsure which steps remain, sm sail reads the repo state and tells you the next move.

When to use

Initial setup (step -1): Run sm init --non-interactive when the repo has sm installed but no .sb_config.json. This generates a config tuned to the detected stack. Run it before refit or the maintenance loop.
Default action: Run sm sail when you're not sure what's next — it reads workflow state and does the right thing.
Refit (step 0): Run sm refit --start to generate a remediation plan, then sm refit --iterate until complete, then sm refit --finish to enter maintenance.
During implementation: Run sm swab after every meaningful code change. Keep running until clean.
Before PR: Run sm scour for a comprehensive sweep.
After CI/review: Run sm buff <PR_NUMBER> to convert feedback into next steps.
Loop exhausted (last resort): Run sm wake-angry-drunk-captain only when barnacles are filed, gates are green or truly unfixable, and the one move left is a human judgment call no verb can make. It demands structured proof, then ends your turn and hands you the captain's question to relay to the human. See below.

Read the full file on GitHub · 113 lines

Changes

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.

9d ago First seen · 113 lines · 186 tokens per session scan A 64907a56a144

Subscribe to this mod's changes

slopmop is a skill published in the GitHub repository ScienceIsNeato/slop-mop (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 186 tokens to every session and 1,598 once invoked, about $0.0009 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.

Debugging ai-tools claude-code-plugin claude-code-plugins claude-skill code-quality git-hooks

root-cause-first

A debugging discipline that requires finding the underlying cause of a bug before changing the code. It also sets rules for handling errors, fallbacks, retries, and temporary diagnostics.

jx-hxxx/hi-vibe · 88 tokens

dead-code

Identify unused code (functions, imports, exports, variables, types, classes) and propose cleanup. Use this skill when the user says "find dead code", "unused code", "clean up unused", "code hygiene", "find unused imports", "what can I delete", or any variation of wanting to identify and remove code that is no longer…

lukaskellerstein/claude-my-marketplace · 75 tokens

slopmop

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Slop-mop skill

Setting up slop-mop in a repo (the install handoff)

When to use

What this file has done since we first saw it

Other skills, from other repositories

root-cause-first

dead-code

question

diagnose

trace-fix

recipe-diagnose