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/fullstackgit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWhat 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 | $0.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
fullstack 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 2d 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.
What it actually says
/fullstack
Full-stack feature development — end-to-end from database to UI. Used when a task requires both frontend and backend implementation.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `fullstack-developer`** | Skills: `clean-code, api-patterns, database-design, frontend-design +3 more`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Read the agent's full instructions from
.windsurf/agents/fullstack-developer.md(or.cursor/rules/agents/fullstack-developer.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/fullstack — Full-Stack Feature Development
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `fullstack-developer`** | Skills: `clean-code, api-patterns, database-design, frontend-design +3 more`
Task
Build complete features end-to-end, from database schema to UI component.
Steps:
-
Database Layer
- Design schema (tables, relations, indexes)
- Create migration
- Seed test data
-
API Layer
- Design DTOs (request/response)
- Implement endpoints
- Business logic + data access
-
Frontend Layer
- API client integration
- State management
- UI components + forms
-
Integration
- E2E test
- Error handling flow
- Loading states
- Optimistic updates
Usage Examples
/fullstack build user profile feature
/fullstack create checkout flow end-to-end
/fullstack implement real-time notifications
/fullstack add search with filters
/fullstack build admin dashboard
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.
- 2d ago First seen · 78 lines · 0 tokens per session scan A 636c3906d4aa
fullstack 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 445 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-flow-auto
Toggle autonomous mode for a session's flow. Usage /dashboard:flow-auto.
dashboard-git-branches
List git branches for the current dir (current marked ). Runs locally, no LLM.
budget
Check the Network-AI federated token budget and recent spend.
run-action
Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as /rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with structured RunRecords (GH.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
check
Run the full local quality gate — TypeScript check, build, dependency audit (prod-only), skill registry validate. Fast pre-commit / pre-suggestdeploy sweep.