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/business-logic)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/business-logic"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/business-logic/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/business-logic"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/business-logic.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.00474 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
business-logic 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 9d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/business-logic
Business logic and domain-driven design — domain modeling, entities, value objects, aggregates, and application services. Used for building the core logic layer of applications.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `business-logic-developer`** | Skills: `clean-code, api-patterns, database-design, dto-patterns`
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/business-logic-developer.md(or.cursor/rules/agents/business-logic-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
/business-logic — Domain & Business Logic
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `business-logic-developer`** | Skills: `clean-code, api-patterns, database-design, dto-patterns`
Task
Model business domains, implement domain logic, and design clean architecture.
Steps:
-
Domain Modeling
- Identify entities and value objects
- Define aggregates and boundaries
- Discover business invariants
-
Business Rules
- Encode invariants in domain methods
- Specification pattern
- Policy pattern
-
Application Services
- Use case orchestration
- Transaction boundaries
- Side effects (events)
-
Domain Events
- Event definition
- Publishing and handling
- Cross-aggregate communication
-
Architecture
- Clean architecture / hexagonal
- Dependency direction
- Testing strategy
Usage Examples
/business-logic model order domain
/business-logic implement DDD aggregates
/business-logic design value objects
/business-logic setup domain events
/business-logic implement use cases
/business-logic design specification pattern
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.
- 9d ago First seen · 83 lines · 0 tokens per session scan A f86298ae3d97
business-logic 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 474 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
brainstorm
Command dispatcher for brainstorm.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
sparc-integration
🔗 System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
trex.kind.new
Generate a complete CRUD entity (Kind) using the automated generator script.
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.