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/backlog)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/backlog"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/backlog/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/backlog"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/backlog.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.00456 |
| Opus 5.5 | $0.00000 | $0.00182 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
backlog 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/backlog
Manage product backlog, refine user stories, and prioritize work. Used for sprint planning, backlog grooming, and roadmap management.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `product-owner`** | Skills: `plan-writing, brainstorming, clean-code`
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
/backlog - Backlog Management
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `product-owner`** | Skills: `plan-writing, brainstorming, clean-code`
Task
Organize, refine, and prioritize the product backlog for iterative delivery.
Steps:
-
Backlog Review
- List all current items
- Identify duplicates and outdated stories
- Break epics into incremental stories
-
Refinement
- Rewrite vague stories with clear AC
- Estimate complexity (story points / t-shirt sizing)
- Map dependencies and blockers
-
Prioritization
- Apply RICE: Reach, Impact, Confidence, Effort
- Order by value / complexity ratio
- Identify quick wins vs. long-term investments
-
Sprint Planning
- Select stories for next sprint
- Ensure team capacity matches commitment
- Define definition of done
Usage Examples
/backlog groom these 20 user stories
/backlog prioritize with RICE framework
/backlog plan sprint 3 with team of 5
/backlog break epic "payment system" into stories
/backlog detect scope creep in current sprint
Caution
- Don't lose sight of MVP goal during refinement
- Validate major scope shifts with stakeholders
- Balance new features against technical debt
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 · 85 lines · 0 tokens per session scan A 2073a4541b86
backlog is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 456 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
dashboard-proposal-detach
Detach the OpenSpec change from a session. Usage /dashboard:proposal-detach.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
qos-workspace
Browse the workspace files and agent logs of a completed QOS task.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.