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/commands/scienceisneato/slop-mop/sm-buff)<a href="https://agentmods.dev/commands/scienceisneato/slop-mop/sm-buff"><img src="https://agentmods.dev/badge/commands/scienceisneato/slop-mop/sm-buff/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/commands/scienceisneato/slop-mop/sm-buff"><img src="https://agentmods.dev/badge/commands/scienceisneato/slop-mop/sm-buff.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.00000 | $0.00555 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
sm-buff 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sm-buff — CI + review-thread triage (under the hood of sail)
You usually don't run buff directly — run sm sail. sm sail drives the
whole PR to green and calls buff watch / triage for you, stopping only when it
needs you to act (see /sm-sail). Reach for sm buff here only for surgical
work: inspecting a specific failure, or resolving a single review thread when
sail has parked on threads.
The buff verbs sail runs for you
| Moment | Run |
|---|---|
| Block until CI settles | sm buff watch <PR#> — exit 0 = CI green + threads clear |
| Snapshot without blocking | sm buff status <PR#> |
| What failed + remediation | sm buff inspect <PR#> |
| Take the next thread batch | sm buff iterate <PR#> |
| Resolve one thread | sm buff resolve <PR#> <THREAD_ID> --scenario <s> --message "…" |
| Confirm threads cleared | sm buff verify <PR#> |
sm buff watch reports the terminal state sail keys off:
Final PR state: clean - CI checks passed and PR feedback is resolved (exit 0).
Resolving a thread — honestly
When sail parks on review threads, resolve each with a real scenario and evidence — never close one to fake green:
fixed_in_code— you changed the code. Cite the commit.invalid_with_explanation— the finding is wrong. Explain why, with evidence.no_longer_applicable— code moved since the comment. Say what changed.out_of_scope_ticketed— valid but not this PR. File an issue, link it.needs_human_feedback— a decision only the human can make. Resolve with--no-resolveand a specific question; finish everything else, then surface it. This is one of only two reasons to stop before green (the other is a blocker you can't clear). See/sm-sail.
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 · 46 lines · 0 tokens per session scan A d6e0a8cbd24d
sm-buff is a command published in the GitHub repository ScienceIsNeato/slop-mop (14 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 555 tokens. 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 commands, from other repositories
ship-ci-review-loop
Command "ship-ci-review-loop" from composio-community/awesome-claude-plugins, covering phase 4: ci & review monitor loop - reference, this phase is mandatory, pr auto-review process, why all comments matter and the monitor loop algorithm.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
init
Install the formatters this repository needs, with every command visible before it runs.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.