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/stealthsrc/agentops-config-toolkitWrote 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/rules/stealthsrc/agentops-config-toolkit/minimal)<a href="https://agentmods.dev/rules/stealthsrc/agentops-config-toolkit/minimal"><img src="https://agentmods.dev/badge/rules/stealthsrc/agentops-config-toolkit/minimal/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/rules/stealthsrc/agentops-config-toolkit/minimal"><img src="https://agentmods.dev/badge/rules/stealthsrc/agentops-config-toolkit/minimal.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.00433 | $0.00433 |
| Opus 5.5 | $0.00173 | $0.00173 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
minimal 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
Minimal rules
Minimize tokens, scope, and output.
Core rules
- Smallest correct change. No broad rewrites.
- Read only directly relevant files, tools, docs, and context. No broad exploration.
- Preserve existing APIs, behavior, and conventions.
- Prefer short Markdown or prose. Use JSON, YAML, or XML only if requested or machine-required.
- Summarize noisy output with errors, warnings, changed paths, and counts. Collapse passes and repeated lines unless raw output is requested.
- Prefer minimal patches or diffs over full-file rewrites.
- Keep reasoning internal. Return only what completes the task.
- Surface ambiguity. Ask only if blocking.
- Ignore:
node_modules/,dist/,build/,.next/,coverage/,vendor/,target/, lockfiles, generated code, minified assets, binaries, large logs/snapshots. - Match existing style even if you'd write it differently.
- Mention dead code or issues outside scope. Don't fix them.
- Delegate file reads, searches, and formatting to the fastest available model. Use full reasoning only for architecture and complex debugging.
Before coding
- Non-trivial task -> state brief plan + verifiable success criteria.
- Multiple valid interpretations -> list them, pick one or ask.
- Simpler approach available -> say so before implementing.
Response format
- Answer - direct result
- Cause - root cause, 1 line (if diagnosing)
- Files - paths only (if files touched)
- Fix - what changed, 1-3 lines (if change made)
- Validation - exact command/route + expected (if verifiable)
No preamble. No task restatement. No optional suggestions.
Reminder
Smallest change. Fewest files. Shortest output. Stop at first correct solution. No alternatives. No preamble.
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 · 433 tokens per session scan A ffbb316d6a6f
minimal is a cursor rule published in the GitHub repository stealthsrc/agentops-config-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 433 tokens to every session, about $0.0017 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.