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/commands/mn-lizard-team/aiyu-multi-agent/test)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/test"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/test/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/commands/mn-lizard-team/aiyu-multi-agent/test"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/test.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.00000 | $0.00815 |
| Opus 5 | $0.00000 | $0.00407 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
test 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test
Test generation and test running command. Creates and executes tests for code.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `test-engineer`** | Skills: `clean-code, testing-patterns, tdd-workflow, webapp-testing +2 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
/test - Test Generation and Execution
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `test-engineer`** | Skills: `clean-code, testing-patterns, tdd-workflow, webapp-testing +2 more`
Purpose
This command generates tests, runs existing tests, or checks test coverage.
Sub-commands
/test - Run all tests
/test [file/feature] - Generate tests for specific target
/test coverage - Show test coverage report
/test watch - Run tests in watch mode
Behavior
Generate Tests
When asked to test a file or feature:
-
Analyze the code
- Identify functions and methods
- Find edge cases
- Detect dependencies to mock
-
Generate test cases
- Happy path tests
- Error cases
- Edge cases
- Integration tests (if needed)
-
Write tests
- Use project's test framework (Jest, Vitest, etc.)
- Follow existing test patterns
- Mock external dependencies
Output Format
For Test Generation
## 🧪 Tests: [Target]
### Test Plan
| Test Case | Type | Coverage |
|-----------|------|----------|
| Should create user | Unit | Happy path |
| Should reject invalid email | Unit | Validation |
| Should handle db error | Unit | Error case |
### Generated Tests
`tests/[file].test.ts`
[Code block with tests]
---
Run with: `npm test`
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 · 174 lines · 0 tokens per session scan A 37057fe6be10
test 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 815 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 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.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
feature-flags
Design feature flag strategy with lifecycle management. Usage - /mindforge:feature-flags [feature] [--type release|experiment|operational] [--rollout 5%].