slopmop-buff

A post-pull-request workflow rule that turns continuous-integration results and review comments into next steps.

In plain words
What is it for?
Triage after pull requests, including handling test results and resolving review threads.
Why use it?
It helps organise the work left after a pull request has been checked and reviewed.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/scienceisneato/slop-mop/slopmop-buff
Clone the repo
git clone --depth 1 https://github.com/ScienceIsNeato/slop-mop

Made for: Cursor.

Per session 35 This file is loaded in full into every session.
When invoked 35 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00035
Opus 5 $0.00017 $0.00017
Sonnet 5 $0.00007 $0.00007
Haiku 4.5 $0.00003 $0.00003

Measured yesterday against content hash 6954145e31c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slopmop-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 yesterday.

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.

slopmop/agent_install/templates/cursor/.cursor/rules/slopmop-buff.mdc · 7 lines

What it actually says

{{CORE}}

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.

  1. yesterday First seen · 7 lines · 35 tokens per session scan A 6954145e31c4

Subscribe to this mod's changes

slopmop-buff is a cursor rule published in the GitHub repository ScienceIsNeato/slop-mop (6 stars, last pushed 12d ago), licensed Apache-2.0. It adds 35 tokens to every session, 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.