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/deployment-rules)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/deployment-rules"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/deployment-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.01287 |
| Opus 5 | $0.00000 | $0.00643 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
deployment-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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Rules — Aiyu Agent Kit
Ship with confidence. Deploy safely, rollback quickly, monitor always.
🔴 CRITICAL: Deployment Safety
5-Phase Deployment
Phase 1: Pre-flight
├── All tests pass
├── Security scan clean
├── Code reviewed and approved
└── Migration scripts tested
Phase 2: Staging
├── Deploy to staging
├── Run smoke tests
├── Verify migrations
└── Performance baseline
Phase 3: Canary
├── Deploy to 5% of production
├── Monitor error rates
├── Check latency metrics
└── Verify business metrics
Phase 4: Rollout
├── Gradually increase to 100%
├── Monitor at each step
└── Automatic rollback triggers
Phase 5: Post-deploy
├── Verify all features working
├── Update changelog
├── Notify stakeholders
└── Archive release branch
Rollback Criteria
| Metric | Threshold | Action |
|---|---|---|
| Error rate | > 1% of requests | Auto-rollback |
| Latency p95 | > 2x baseline | Alert + manual decision |
| CPU/Memory | > 90% for 5 min | Alert + scale |
| Business metric | Revenue drop > 5% | Immediate rollback |
🟡 HIGH: Release Management
Semantic Versioning
MAJOR.MINOR.PATCH
MAJOR — Breaking changes (incompatible API)
MINOR — New features (backward compatible)
PATCH — Bug fixes (backward compatible)
Pre-release: 1.2.0-alpha.1, 1.2.0-beta.3, 1.2.0-rc.1
Build: 1.2.0+build.123
Changelog Format
## [1.3.0] - 2025-04-28
### Added
- OAuth2 login with Google provider
- Export reports as PDF
### Changed
- Improved search performance by 40%
- Updated API rate limits from 100/min to 200/min
### Fixed
- Memory leak in WebSocket connections
- Incorrect timezone in scheduled reports
### Breaking
- Removed deprecated `/api/v1/search` endpoint
- Minimum Node.js version is now 18
Environment Strategy
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Dev │───►│ Staging │───►│ Pre-prod│───►│ Prod │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
Developer CI/CD UAT/Load test Production
testing auto-deploy validation release
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 · 215 lines · 0 tokens per session scan A 93abbb9d0f76
deployment-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,287 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
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.
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.