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/code-quality-rules)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/code-quality-rules"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/code-quality-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.01237 |
| Opus 5 | $0.00000 | $0.00619 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
code-quality-rules 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Rules — Aiyu Agent Kit
Standards for maintainable, readable, and testable code.
🔴 CRITICAL: Code Fundamentals
Naming Conventions
# ✅ GOOD — Clear, descriptive names
def calculate_user_total_spending(user_id: int) -> float:
user_orders = get_orders_by_user(user_id)
return sum(order.amount for order in user_orders)
# ❌ BAD — Abbreviations, unclear intent
def calc(u_id):
o = get_o(u_id)
return sum(x.a for x in o)
Naming standards:
- Functions/Methods:
verb_nounformat (get_user,validate_input) - Classes:
Nounin PascalCase (UserManager,PaymentGateway) - Constants:
UPPER_SNAKE_CASE(MAX_RETRY_COUNT) - Booleans: Prefix with
is_,has_,can_(is_active,has_permission)
Function Design
# ✅ GOOD — Single responsibility, clear purpose
def validate_email(email: str) -> bool:
"""Check if email format is valid."""
return re.match(r'^[\w\.-]+@[\w\.-]+\.\w+$', email) is not None
def send_welcome_email(user: User) -> None:
"""Send welcome email to new user."""
# Implementation
# ❌ BAD — Multiple responsibilities
def process_user(user_data):
validate_email(user_data['email'])
save_to_database(user_data)
send_welcome_email(user_data)
update_analytics(user_data)
Function limits:
- Max 20 lines per function
- Max 3 parameters (use objects for more)
- Do one thing, do it well
🟡 HIGH: Maintainable Code
Comments & Documentation
# ✅ GOOD — Explain WHY, not WHAT
def calculate_discount(price: float, user: User) -> float:
"""
Apply discount based on user tier.
Premium users get 20% off as per business rule #123.
Regular users get 10% off during promotional periods.
"""
if user.is_premium:
return price * 0.8 # 20% discount for premium
return price * 0.9 # 10% standard discount
# ❌ BAD — Redundant comments
def add(a, b):
# Add a and b together
return a + b
Error Handling
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 · 194 lines · 0 tokens per session scan A 5cd1443eeb9e
code-quality-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 1,237 tokens. 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-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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.