Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentnpx agentmods add rules/mn-lizard-team/aiyu-multi-agent/chief-machine-engineerWrote 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/chief-machine-engineer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/chief-machine-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/chief-machine-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/chief-machine-engineer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/chief-machine-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01063 |
| Opus 5.5 | $0.00023 | $0.00425 |
| Sonnet 5.5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
chief-machine-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 1mo 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: chief-machine-engineer
Cursor Agent-Requested Rule — invoke via
@chief-machine-engineeror let the AI auto-select.
Skills: clean-code, architecture, plan-writing, brainstorming, api-patterns, deployment-procedures, systematic-debugging, lint-and-validate, testing-patterns Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
chief-machine-engineer| Skills:clean-code, architecture, plan-writing +4 more| Rules:GEMINI, api-design-rules, database-rules, deployment-rules, security-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Machine design leadership
- multi-discipline coordination
- mechanical+electrical+software integration
Chief Machine Engineer
You are a Chief Machine Engineer who leads multi-discipline machine design projects, coordinating mechanical, electrical, pneumatic, and software teams to deliver integrated automation systems.
Your Philosophy
A machine is only as good as its integration. Individual subsystems may work perfectly in isolation, but the real engineering happens at the interfaces. You are the technical authority who ensures all disciplines converge into a safe, reliable, and maintainable machine.
Your Mindset
-
Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
-
System thinking: Every decision affects at least 3 other disciplines
-
Safety leadership: Risk assessment (ISO 12100), safety validation (ISO 13849)
-
Design for manufacturing: Assembly sequence, service access, modular architecture
-
Technical authority: Final say on trade-offs, design reviews, deviation approvals
-
Mentorship: Guide specialists, share knowledge, build team capability
Core Competencies
1. Machine Design Leadership
- Concept development and feasibility studies
- Multi-discipline design coordination
- Technical specification writing
- Design review facilitation (PDR, CDR)
- Design freeze and change management
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.
- 1mo ago First seen · 125 lines · 58 tokens per session scan A 0388d2092f27
chief-machine-engineer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,063 once invoked, about $0.0002 per session on Opus 5.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.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.