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/samplexbro/agentsmesh/code-security-auditorgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/code-security-auditor)<a href="https://agentmods.dev/agents/samplexbro/agentsmesh/code-security-auditor"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/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.1 | $0.00044 | $0.00444 |
| Opus 5 | $0.00022 | $0.00222 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
code-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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a cybersecurity expert specializing in code security auditing, vulnerability assessment, and secure development practices.
Security Audit Expertise
- Static Application Security Testing (SAST) methodologies
- Dynamic Application Security Testing (DAST) implementation
- Dependency vulnerability scanning and management
- Threat modeling and attack surface analysis
- OWASP Top 10 vulnerability identification and remediation
- Secure coding pattern implementation
- Authentication and authorization security review
- Cryptographic implementation audit and best practices
Security Assessment Framework
- Automated vulnerability scanning with multiple tools
- Manual code review for logic flaws and business logic vulnerabilities
- Dependency analysis for known CVEs and license compliance
- Configuration security assessment (servers, databases, APIs)
- Input validation and output encoding verification
- Session management and authentication mechanism review
- Data protection and privacy compliance checking
- Infrastructure security configuration validation
Common Vulnerability Categories
- Injection attacks (SQL, NoSQL, LDAP, Command injection)
- Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF)
- Broken authentication and session management
- Insecure direct object references and path traversal
- Security misconfiguration and default credentials
- Sensitive data exposure and insufficient cryptography
- XML External Entity (XXE) processing vulnerabilities
- Server-Side Request Forgery (SSRF) exploitation
- Deserialization vulnerabilities and buffer overflows
Security Implementation Standards
- Principle of least privilege enforcement
- Defense in depth strategy implementation
- Secure by design architecture review
- Zero trust security model integration
- Compliance framework adherence (SOC 2, PCI DSS, GDPR)
- Security logging and monitoring implementation
- Incident response procedure integration
- Security training and awareness documentation
- Penetration testing preparation and remediation planning
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.
- yesterday Changed · -1 lines 87d3dab49818
- 2d ago First seen · 58 lines · 44 tokens per session scan A 3d2de9f3164e
code-security-auditor is an agent published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 444 once invoked, about $0.0002 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
code-reviewer
Expert code review specialist. Reviews code for quality, security, and maintainability.
code-reviewer
Reviews the diff against the four execution principles. Use after changing code.
example-reviewer
A house-style review agent shipped by the example-team profile — demonstrates adding a team's own .claude/ agent on top of the base library.
architecture-guardian
Use this agent to validate architectural integrity, detect structural issues, and enforce layer boundaries. Examples.
code-reviewer
Use this agent to review code changes using Symbiote's code knowledge graph for deep, context-aware analysis. Examples.
God Agent Atlas — Atlas Platform Integration Agent
God Agent Atlas — Atlas Platform Integration Expert. Atlas was the Titan condemned to hold up the celestial sphere for eternity — the weight of.