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/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/documentation-rules)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/documentation-rules"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/documentation-rules.svg" alt="Measured on agentmods" 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.00975 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade B, and why
documentation-rules scanned grade B with 1 finding 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl start postgresql How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Rules — Aiyu Agent Kit
Standards for clear, helpful, and maintainable documentation.
🔴 CRITICAL: Documentation Essentials
README.md Requirements
Every project must have a README with:
# Project Name
> One-line description of what this project does
## Features
- Feature 1: Brief description
- Feature 2: Brief description
## Installation
```bash
npm install
# or
pip install -r requirements.txt
Usage
npm start
# or
python main.py
Configuration
Environment variables needed:
API_KEY— Your API keyDATABASE_URL— Connection string
License
### Code Comments
```python
# ✅ GOOD — Explain WHY, not WHAT
# Retry 3 times because external API is occasionally flaky
MAX_RETRIES = 3
# ✅ GOOD — Document complex logic
# Using sliding window approach to maintain O(n) complexity
# instead of naive O(n²) nested loop approach
def find_substring(s: str, pattern: str) -> int:
...
# ❌ BAD — Obvious comments
x = x + 1 # Increment x by 1
🟡 HIGH: API Documentation
Function/Method Documentation
def create_user(
email: str,
password: str,
role: str = "user"
) -> User:
"""
Create a new user account.
Args:
email: User's email address (must be unique)
password: Plain text password (will be hashed)
role: User role, defaults to "user"
Returns:
User object with generated ID
Raises:
ValidationError: If email format is invalid
DuplicateError: If email already exists
Example:
>>> user = create_user("[email protected]", "secure123")
>>> user.email
'[email protected]'
"""
...
API Endpoint Documentation
## POST /api/users
Create a new user.
### Request
```json
{
"email": "[email protected]",
"password": "securepassword",
"role": "user"
}
Response
201 Created
{
"id": "usr_123",
"email": "[email protected]",
"role": "user",
"created_at": "2024-01-15T10:30:00Z"
}
400 Bad Request
{
"error": "Invalid email format",
"field": "email"
}
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.
- 3d ago First seen · 228 lines · 0 tokens per session scan B d78bd62c892c
documentation-rules is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 975 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.