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 commands/mn-lizard-team/aiyu-multi-agent/automationgit 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/commands/mn-lizard-team/aiyu-multi-agent/automation)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/automation"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/automation.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.00606 |
| Opus 5 | $0.00000 | $0.00303 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
automation 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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/automation
Set up test automation, E2E pipelines, and CI/CD testing. Used for Playwright, Cypress, visual regression, and load testing.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `qa-automation-engineer`** | Skills: `webapp-testing, testing-patterns, web-design-guidelines, clean-code +1 more`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Follow the task steps defined below
- Apply the Socratic Gate: ask clarifying questions if requirements are unclear
- Report completion status at the end
/automation - Test Automation
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `qa-automation-engineer`** | Skills: `webapp-testing, testing-patterns, web-design-guidelines, clean-code +1 more`
Task
Build robust automated testing infrastructure from scratch or enhance existing pipelines.
Steps:
-
Assess Current State
- Check existing test coverage
- Identify gaps (unit vs. integration vs. E2E)
- Review CI/CD pipeline status
-
Tool Selection
- Playwright (preferred): multi-tab, parallel, trace viewer
- Cypress: component testing, reliable waiting
- Puppeteer: headless tasks
- k6 / Artillery: load testing
-
Test Architecture
- Page Object Model (POM) — no raw selectors in tests
- Data isolation — each test creates its own data
- Deterministic waits —
expect(locator).toBeVisible()notsleep
-
Suite Definition
- Smoke Suite (P0): login, critical path, checkout — every commit
- Regression Suite (P1): all stories, edge cases, cross-browser — nightly
- Visual Regression: snapshot testing for UI shifts
-
Unhappy Path Automation
- Slow network (3G simulation)
- Server crash (mock 500 mid-flow)
- Double click / rage clicking
- Auth expiry during form fill
- XSS payloads in inputs
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.
- 6d ago First seen · 93 lines · 0 tokens per session scan A 693c0348edd7
automation is a command 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 606 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-08-31.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
lock-e2e
Promote a verified action into a frozen, locked e2e regression test. Runs the action once strict (no repair) via cdplocke2etest and freezes it to .rn-agent/e2e/ .yaml only if it passes. v1 supports param-free actions only.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
test
Agentic end-to-end test orchestrator — drive web/macOS flows, evaluate UX rubric, reconcile issues.
r-test
You are the test command. You dispatch the UAT subagent to run acceptance tests against the current working state from an end-user perspective.