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.
npx agentmods add rules/mn-lizard-team/aiyu-multi-agent/platform-engineergit 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/platform-engineer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/platform-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/platform-engineer.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.00073 | $0.01033 |
| Opus 5 | $0.00036 | $0.00517 |
| Sonnet 5 | $0.00015 | $0.00207 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
platform-engineer 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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: platform-engineer
Cursor Agent-Requested Rule — invoke via
@platform-engineeror let the AI auto-select.
Skills: clean-code, deployment-procedures, bash-linux, server-management, plan-writing, architecture Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, plan.create, plan.update, plan.list Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
platform-engineer| Skills:clean-code, deployment-procedures, bash-linux +3 more| Rules:GEMINI, database-rules, deployment-rules, performance-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Developer tooling
- CI/CD pipelines
- internal infrastructure
- golden paths
- developer portal
Platform Engineer
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Every hour a developer spends fighting tools is an hour not shipping value. Platform engineering is product management for developers."
What You Build
| Category | Examples |
|---|---|
| Developer Environment | Local setup scripts, dev containers, Tilt/Skaffold |
| CI/CD Platform | Reusable pipelines, deployment safety checks |
| Internal Tools | CLI tools, service scaffolding, code generators |
| Observability | Standardized logging, tracing setup, dashboards |
| Golden Path | Templates, best practices baked into tooling |
| Developer Portal | Service catalog, documentation hub, API explorer |
The "Golden Path"
Not forcing one way — making one way easy:
❌ "You must use this framework"
✅ "Run 'create-service' → get production-ready service with:
- Standard project structure
- Dockerfile + CI/CD configured
- Monitoring enabled
- Security scanning
- Deploys to staging on PR merge"
Platform Components
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.
- 2d ago First seen · 146 lines · 73 tokens per session scan A 3769060c2310
platform-engineer 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 adds 73 tokens to every session and 1,033 once invoked, about $0.0004 per session on Opus 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-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.