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/d-o-hub/github-template-ai-agents/security-code-auditornpx skills add d-o-hub/github-template-ai-agents --skill security-code-auditorgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/skills/d-o-hub/github-template-ai-agents/security-code-auditor)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/security-code-auditor"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/security-code-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.00131 | $0.00937 |
| Opus 5 | $0.00066 | $0.00468 |
| Sonnet 5 | $0.00026 | $0.00187 |
| Haiku 4.5 | $0.00013 | $0.00094 |
Grade A, and why
security-code-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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Code Auditor
Perform security audits on code, configurations, and repositories to identify vulnerabilities and security issues.
When to Use
- User asks to audit, review, or check security of code
- Need to perform vulnerability scans or OWASP Top 10 checks
- Even if they just say "check for security issues" or "is this secure"
Scope
- Includes: Source code review, dependency scanning, configuration auditing, OWASP Top 10 checks
- Excludes: Network penetration testing, active exploitation, social engineering
Audit Workflow
1. Initial Assessment
- Identify the technology stack and frameworks
- Determine the application's attack surface
- Review authentication and authorization mechanisms
2. Static Analysis
- Check for injection vulnerabilities (SQL, NoSQL, OS command, LDAP)
- Identify insecure deserialization
- Review cryptographic implementations
- Validate input sanitization
3. Configuration Review
- Review security headers (CSP, HSTS, X-Frame-Options)
- Check CORS policies
- Validate session management settings
- Examine environment variable handling
4. Dependency Scanning
- Check for known CVEs in dependencies
- Review outdated packages
- Validate license compliance
Common Vulnerability Patterns
Injection Flaws
# BAD: Direct string concatenation
query = "SELECT * FROM users WHERE id = " + user_id
# GOOD: Parameterized queries
cursor.execute("SELECT * FROM users WHERE id = ?", (user_id,))
Secrets Management
- Never hardcode credentials in source code
- Use environment variables or secure vaults
- Rotate keys regularly
- Use placeholders like
[REDACTED]orexample-tokenin examples
Authentication Issues
- Enforce strong password policies
- Implement multi-factor authentication
- Use secure session tokens with proper expiration
- Validate all authenticated endpoints
Severity Classification
| Level | Criteria | Response Time |
|---|---|---|
| Critical | Remote code execution, authentication bypass | Immediate |
| High | Data exposure, privilege escalation | 24 hours |
| Medium | Information disclosure, CSRF | 1 week |
| Low | Best practice violations | Next sprint |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 123 lines · 131 tokens per session scan A 1374acd3190a
security-code-auditor is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 937 once invoked, about $0.0007 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.