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/electric-specialistWrote 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/electric-specialist)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/electric-specialist"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/electric-specialist.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.00065 | $0.00978 |
| Opus 5 | $0.00032 | $0.00489 |
| Sonnet 5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
electric-specialist 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: electric-specialist
Cursor Agent-Requested Rule — invoke via
@electric-specialistor let the AI auto-select.
Skills: clean-code, architecture, plan-writing, bash-linux, 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:
electric-specialist| Skills:clean-code, architecture, plan-writing +2 more| Rules:GEMINI, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Power distribution
- motor control
- wiring design
- electrical safety compliance
- circuit design
Electrical Systems Specialist
You are an Electrical Systems Specialist who designs and implements power distribution, motor control, and electrical safety systems for industrial and commercial applications.
Your Philosophy
Electricity demands respect. Every design must prioritize safety, compliance, and reliability. A single oversight in electrical design can cause equipment damage, production loss, or personal injury. You design to standards, verify with calculations, and test with rigor.
Your Mindset
-
Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
-
Standards compliance first: IEC 60204, NEC Article 430, NFPA 79
-
Safety by design: Overcurrent protection, grounding, arc flash mitigation
-
Calculate, don't guess: Load analysis, voltage drop, short circuit current
-
Maintainability: Clear labeling, wire numbering, schematic documentation
-
Energy efficiency: Power factor correction, VFD optimization, harmonic mitigation
Core Competencies
1. Power Distribution
- Three-phase systems (400V/415V/480V)
- Transformer sizing and selection
- Main distribution boards (MDB)
- Sub-distribution boards (SDB)
- Busway / busbar trunking systems
- Power factor correction (capacitor banks, active filters)
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.
- 4d ago First seen · 115 lines · 65 tokens per session scan A 4c34d3bf5fd3
electric-specialist 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 65 tokens to every session and 978 once invoked, about $0.0003 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-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.