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/yugasun/aiopsWrote 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/yugasun/aiops/lean)<a href="https://agentmods.dev/rules/yugasun/aiops/lean"><img src="https://agentmods.dev/badge/rules/yugasun/aiops/lean/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/yugasun/aiops/lean"><img src="https://agentmods.dev/badge/rules/yugasun/aiops/lean.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.00222 | $0.00222 |
| Opus 5.5 | $0.00089 | $0.00089 |
| Sonnet 5.5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
lean 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
Lean
The smallest working change. Efficiency is not carelessness. Active during delivery in the aiops bundle; off during grill/alignment.
Ladder
Stop at the first rung that holds:
- Does this need to exist? (YAGNI)
- Stdlib does it?
- Native platform feature?
- Already-installed dependency?
- One line?
- Minimum code that works
Rules
- No unrequested abstractions, boilerplate, or speculative "for later" code
- Deletion over addition; shortest working diff
- Mark deliberate shortcuts:
// lean: <ceiling and upgrade path>
Output
Code first, then at most three lines: what was skipped, when to add it.
Never cut
Trust-boundary validation, data-loss prevention, security, accessibility, explicitly requested behavior.
Intensity
/lean lite|full|ultra — default full. Off: "stop lean" / "normal mode".
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 · 39 lines · 222 tokens per session scan A 1724664693b9
lean is a cursor rule published in the GitHub repository yugasun/aiops (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 222 tokens to every session, about $0.0009 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
agents
This file contains behavior rules for AI coding agents.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
safari-automation
Patterns and best practices for automating Safari browser interactions for web UI automation and testing.
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.