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.
npx agentmods add rules/joodascode/slopwatch/cursorrulesgit clone --depth 1 https://github.com/JoodasCode/SlopWatchWhat 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 | $0.00916 | $0.00916 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
cursorrules 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 138 lines · 916 tokens per session scan A 2ed4ec603641
cursorrules is a cursor rule published in the GitHub repository JoodasCode/SlopWatch (10 stars, last pushed 1y ago), with no licence file. It adds 916 tokens to every session, about $0.0046 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.
Other cursor rules, from other repositories
workflow-memory
Workflow memory operating loop — read root state before acting, write state back after meaningful change.
xcf-ai-guide
XCF (Xcode MCP Server) is a powerful Swift-based automation tool designed to streamline Xcode project management for AI assistants. This guide provides comprehensive instructions for integrating XCF into AI-powered development workflows.
xcf-quickref
Cursor rule "xcf-quickref" from CodeFreezeAI/xcf, covering xcf quick reference guide 🚀, 🎛️ xcf core actions, permissions & project management, build & execute and system & analysis.
xcf-user-guide
XCF (Xcode MCP Server) is a powerful, Swift-native automation tool designed to revolutionize your Xcode development workflow. This guide provides an in-depth look at installation, configuration, and usage of XCF.
ReviewGate
This is an advanced, experimental rule. It instructs the AI Agent to check for, potentially create, and then execute a Python script (finalreviewgate.py) in your project's root directory to facilitate an interactive review loop. By using this rule, you acknowledge that the AI will attempt file system operations (read…
ReviewGateV2
Cursor rule "ReviewGateV2" from LakshmanTurlapati/Review-Gate, covering mandatory checkpoint (must be included in every response), enforcement mechanism, 0. user advisory & safety, 1. core principle & context and phase 1: primary task execution.