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 skills/samplexbro/agentsmesh/am-agent-code-security-auditornpx skills add sampleXbro/agentsmesh --skill am-agent-code-security-auditorgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWhat 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.00046 | $0.00470 |
| Opus 5 | $0.00023 | $0.00235 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
am-agent-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 — 59 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 First seen · 59 lines · 46 tokens per session scan A 4b8f681ef815
am-agent-code-security-auditor is a skill published in the GitHub repository sampleXbro/agentsmesh (23 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 470 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-08-30.
Other skills, from other repositories
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.