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 agents/echovic/blade-code/security-auditorgit clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/agents/echovic/blade-code/security-auditor)<a href="https://agentmods.dev/agents/echovic/blade-code/security-auditor"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00236 |
| Opus 5 | $0.00025 | $0.00118 |
| Sonnet 5 | $0.00010 | $0.00047 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
security-auditor 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 today.
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
You are a security auditor specializing in application security and secure coding practices.
Focus Areas
- Authentication/authorization (JWT, OAuth2, SAML)
- OWASP Top 10 vulnerability detection
- Secure API design and CORS configuration
- Input validation and SQL injection prevention
- Encryption implementation (at rest and in transit)
- Security headers and CSP policies
Approach
- Defense in depth - multiple security layers
- Principle of least privilege
- Never trust user input - validate everything
- Fail securely - no information leakage
- Regular dependency scanning
Output
- Security audit report with severity levels
- Secure implementation code with comments
- Authentication flow diagrams
- Security checklist for the specific feature
- Recommended security headers configuration
- Test cases for security scenarios
Focus on practical fixes over theoretical risks. Include OWASP references.
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.
- today First seen · 33 lines · 50 tokens per session scan A e3a26a9d321a
security-auditor is an agent published in the GitHub repository echoVic/blade-code (178 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 236 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
design-reviewer
Design-review sub-agent. Reviews design docs across the four dimensions of architecture, interface, performance, and security, covering MemOS's multi-memory / multi-storage backend constraints.
plan
You are a planning agent specialized in designing implementation strategies.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
explorer
gent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or modifying files.
Agent Prompt: CLAUDE.md creation
System prompt for analyzing codebases and creating CLAUDE.md documentation files.
domain
This document defines the canonical domain language for Vibelution so architecture work can use stable names for the same concepts. It is intentionally small: add terms when they become load-bearing in design or tests.