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 skills add zhaono1/agent-playbook --skill security-auditorgit clone --depth 1 https://github.com/zhaono1/agent-playbookWrote 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/zhaono1/agent-playbook/security-auditor)<a href="https://agentmods.dev/skills/zhaono1/agent-playbook/security-auditor"><img src="https://agentmods.dev/badge/skills/zhaono1/agent-playbook/security-auditor/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/skills/zhaono1/agent-playbook/security-auditor"><img src="https://agentmods.dev/badge/skills/zhaono1/agent-playbook/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk pass
- NVIDIA SkillSpector pass
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.00030 | $0.00905 |
| Opus 5.5 | $0.00012 | $0.00362 |
| Sonnet 5.5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
Expert in identifying security vulnerabilities following OWASP Top 10 and security best practices.
When This Skill Activates
Activates when you:
- Request a security audit
- Mention "security" or "vulnerability"
- Need security review
- Ask about OWASP
OWASP Top 10:2025 Coverage
Use the current OWASP Top 10 as an awareness taxonomy, not as proof of complete security coverage. For verifiable application controls, map findings to the current OWASP ASVS or the project's required standard.
A01: Broken Access Control
- Verify authentication and object/function-level authorization on every sensitive path.
- Test tenant boundaries, IDOR/BOLA, role changes, and server-side URL fetch controls.
- SSRF is included in this 2025 category; validate destinations, schemes, redirects, and network egress.
A02: Security Misconfiguration
- Inspect debug flags, CORS, security headers, default accounts, cloud/IaC policy, and error exposure.
- Compare runtime configuration with hardened environment-specific defaults.
A03: Software Supply Chain Failures
- Review lockfiles, provenance, build workflows, mutable CI dependencies, update policy, and dependency risk.
- Distinguish a vulnerable package from compromised build or distribution infrastructure.
A04: Cryptographic Failures
- Check secret storage, transport encryption, key lifecycle, random generation, algorithms, and data-at-rest requirements.
- Flag hardcoded credentials, weak hashes, insecure modes, and missing certificate verification.
A05: Injection
- Trace untrusted data into SQL/NoSQL, shell, template, LDAP, expression, and browser execution sinks.
- Prefer parameterization and safe APIs; test encoding at the actual output context.
A06: Insecure Design
- Threat-model trust boundaries, abuse cases, rate limits, high-risk workflows, and failure recovery.
- Verify the design prevents unsafe states rather than relying only on downstream validation.
A07: Authentication Failures
What ships with it
6 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.
- 1mo ago First seen · 124 lines · 30 tokens per session scan A 28e686bda75f
security-auditor is a skill published in the GitHub repository zhaono1/agent-playbook (85 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 905 once invoked, about $0.0001 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…