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/testing-rules)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/testing-rules"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/testing-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.01059 |
| Opus 5 | $0.00000 | $0.00530 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
testing-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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Rules — Aiyu Agent Kit
If it's not tested, it's broken. Test with purpose, not just coverage.
🔴 CRITICAL: Testing Fundamentals
Test Pyramid
/\
/ \ E2E Tests (few, slow, expensive)
/────\ — Critical user journeys only
/ \
/ Integ \ Integration Tests (some, moderate)
/──────────\ — Service interactions, DB queries
/ \
/ Unit Tests \ Unit Tests (many, fast, cheap)
/________________\ — Business logic, edge cases
Distribution target: 70% Unit / 20% Integration / 10% E2E
AAA Pattern (Arrange-Act-Assert)
def test_user_creation():
# Arrange
user_data = {"email": "[email protected]", "name": "Test User"}
# Act
result = create_user(user_data)
# Assert
assert result.is_success
assert result.user.email == "[email protected]"
Naming Convention
# test_<unit>_<scenario>_<expected_result>
def test_create_user_with_valid_data_returns_success():
...
def test_create_user_with_duplicate_email_raises_error():
...
def test_create_user_with_empty_name_returns_validation_error():
...
🟡 HIGH: Test Quality
What to Test
| Category | Examples | Priority |
|---|---|---|
| Happy path | Valid inputs, normal flow | Must |
| Edge cases | Empty, null, boundary values | Must |
| Error handling | Invalid input, service down | Must |
| Concurrency | Race conditions, deadlocks | Should |
| Performance | Response time, throughput | Nice to have |
What NOT to Test
- Framework/library internals
- Trivial getters/setters
- Third-party API behavior (mock it)
Mocking Best Practices
# ✅ GOOD — Mock external dependencies, test your logic
@patch('services.email.send_email')
def test_welcome_email_sent_on_registration(mock_send):
register_user(user_data)
mock_send.assert_called_once_with(
to=user_data["email"],
template="welcome"
)
# ❌ BAD — Mocking the system under test
@patch('services.user.validate_email')
def test_registration(mock_validate):
mock_validate.return_value = True # Testing mock, not logic
register_user(user_data)
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 · 184 lines · 0 tokens per session scan A 60c75393f7cf
testing-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,059 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-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.