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/varutasu/agent-pipeline/security-auditnpx skills add varutasu/agent-pipeline --skill security-auditgit clone --depth 1 https://github.com/varutasu/agent-pipelineWrote 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/varutasu/agent-pipeline/security-audit)<a href="https://agentmods.dev/skills/varutasu/agent-pipeline/security-audit"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/security-audit.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.00117 | $0.01430 |
| Opus 5 | $0.00059 | $0.00715 |
| Sonnet 5 | $0.00023 | $0.00286 |
| Haiku 4.5 | $0.00012 | $0.00143 |
Grade A, and why
security-audit 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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security audit
Six-layer audit framework for application code (not infra/IAM — those are separate convoys). Outputs a severity 0–4 findings list, an executive summary, and fix suggestions with file:line citations. Deep reference: references/owasp-checklist.md.
When to invoke
- Automatic: by
role-security-auditoron every PR draft except whenskip: securityis set. - Manual: when the user says "security review", "audit this for vulnerabilities", or before merging auth/API/schema convoys.
- Pre-merge: audit fan-out —
/multitask role-reviewer + role-security-auditor + role-design-system-auditor + role-a11y-auditor.
Severity scale
| Severity | Meaning | Treatment |
|---|---|---|
| 4 — Critical | Exploitable without unusual conditions: auth bypass, secret in client bundle, SQL/command injection on user input, IDOR on another user's data. | Block merge. |
| 3 — High | Serious weakness requiring attacker effort or specific config: missing rate limit on auth, weak session TTL, missing auth on non-public route, mass assignment. | Fix before merge unless documented exception in convoy. |
| 2 — Medium | Defense-in-depth gap: verbose error leaks stack trace, missing security headers, log line includes PII. | Fix or track; recommend before next release. |
| 1 — Low | Hardening opportunity: inconsistent auth helper usage, missing Zod on low-risk query param. | Inline in report. |
| 0 — Info | Note for maintainer; not a defect. | Inline only. |
The 6 layers
Run in order. Stop early only if the diff is literally comment-only.
Layer 1 — Authentication boundary
Every protected route and server action must identify the caller before doing work.
- New or changed API routes / server actions: is there an auth gate (
requireAuth,auth(), session check, Bearer verify)? - Auth endpoints: rate limiting present? (
checkAuthRateLimitor equivalent) - No synthetic-admin / dev-bypass fallbacks in production paths
- JWT/session: secret from env (fail-loud if unset), reasonable TTL, not in client bundle
- Password handling: hashed (bcrypt/argon2), never logged, never returned in API responses
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.
- 6d ago First seen · 109 lines · 117 tokens per session scan A 8148f9ea9e66
security-audit is a skill published in the GitHub repository varutasu/agent-pipeline (2 stars, last pushed 27d ago), licensed MIT. It adds 117 tokens to every session and 1,430 once invoked, about $0.0006 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
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"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.