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/secure-coding)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/secure-coding"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/secure-coding/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/secure-coding"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/secure-coding.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.00511 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
secure-coding 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/secure-coding
Shift-left security coding — input validation, auth patterns, cryptography, and OWASP secure design principles. Used when writing new features or reviewing code for security anti-patterns.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `secure-coder`** | Skills: `clean-code, vulnerability-scanner, api-patterns, code-review-checklist`
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
/secure-coding - Secure Code Review & Patterns
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `secure-coder`** | Skills: `clean-code, vulnerability-scanner, api-patterns, code-review-checklist`
Task
Apply security-first coding practices. Prevent vulnerabilities at design time, not after deployment.
Steps:
-
Identify Trust Boundaries
- Where does user input enter the system?
- What data crosses network/API boundaries?
-
Apply Input Validation
- Type, length, range, format checks
- Reject invalid input immediately
-
Apply Output Encoding
- HTML escape before rendering
- SQL parameterize before querying
- Shell-quote before system calls
-
Authentication Review
- Password hashing (Argon2id/bcrypt)
- JWT expiry and rotation
- RBAC on every route
-
Cryptography Check
- Secure random, not Math.random()
- AES-256-GCM, RSA-4096
- Secrets in env, never in repo
Usage Examples
/secure-coding review this API endpoint
/secure-coding add input validation to form
/secure-coding harden authentication flow
/secure-coding check for SQL injection risk
/secure-coding implement rate limiting
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 · 88 lines · 0 tokens per session scan A 452cd3c0af88
secure-coding 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 511 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
proof-capture
Capture PR-ready proof artifacts for a feature, with an attested fail-closed controller in strict mode.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
code-simplify
Simplify code for clarity and maintainability — reduce complexity without changing behavior.
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.
specify
Create or update the feature specification from a natural language feature description.