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/vigolium/piolium/auditnpx skills add vigolium/piolium --skill auditgit clone --depth 1 https://github.com/vigolium/pioliumWrote 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/vigolium/piolium/audit)<a href="https://agentmods.dev/skills/vigolium/piolium/audit"><img src="https://agentmods.dev/badge/skills/vigolium/piolium/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 | $0.00135 | $0.07960 |
| Opus 5 | $0.00068 | $0.03980 |
| Sonnet 5 | $0.00027 | $0.01592 |
| Haiku 4.5 | $0.00014 | $0.00796 |
Grade B, and why
audit scanned grade B with 1 finding 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 5d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf piolium/codeql-artifacts/db/ Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit — Full Security Audit Methodology
10-phase security audit methodology for arbitrary source code repositories. Each phase defines what to analyze and what to produce. Orchestration (branching, state management, agent dispatch) is handled by the plugin commands.
When to Apply
- Full security audit of a repository
- Advisory regression check combined with static analysis
- Deep vulnerability research on a specific codebase
- Large or unusual architectures where default SAST modeling is likely incomplete
- "Run the security agents" / "audit for vulnerabilities" / "is this secure?"
Idempotency & Resumption
Before executing any phase, apply these rules to avoid redundant work:
- Skip completed phases: if the expected KB sections already exist and neither the codebase nor the threat-model inputs have fundamentally changed, reuse the existing content and mark the phase skipped.
- Re-audit as KB update: for re-audits,
piolium/attack-surface/knowledge-base-report.mdfrom the previous run is the starting knowledge base. Do not regenerate it from scratch. Load it, diff the codebase against thecommitfield of the last completed entry inpiolium/audit-state.json, and update only the sections whose source inputs changed. Mark unchanged sections with[reused from <short-sha>]. Documentation-only changes require no re-audit; changes to auth, core business logic, or attack-surface components invalidate the Static Analysis Summary and Phase 10 Addendum (## Phase 10 Addendum, written by the Review Chambers) sections at minimum. - Partial resumption (Phases 7-9): if
piolium/findings-draft/already contains draft files, resume from the existing drafts rather than starting fresh. - State recording:
piolium/audit-state.jsonis append-only. Before starting a new audit, append a new entry to theauditsarray withstatus: "in_progress". After each phase completes or fails, update that entry'sphasesmap in-place. Never overwrite or remove earlier entries — they are the permanent audit history. Seereferences/report-templates.mdfor the full schema.
What ships with it
15 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.
- assets/icon.svg 1.1 KB
- hooks/scripts/validate_phase_output.py 21 KB runs code
- references/adversarial-review.md 6.9 KB
- references/architecture-aware-sast.md 15 KB
- references/audit-workflow.md 33 KB
- references/chamber-protocol.md 14 KB
- references/creative-attack-modes.md 12 KB
- references/deep-analysis.md 14 KB
- references/domain-attack-playbooks.md 64 KB
- references/knowledge-base-template.md 17 KB
- references/real-env-validation.md 5.0 KB
- references/report-templates.md 14 KB
- references/triage-and-prereqs.md 6.4 KB
- scripts/consolidate_drafts.py 19 KB runs code
- scripts/rg-hotspots.sh 3.1 KB runs code
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.
- 5d ago First seen · 565 lines · 135 tokens per session scan B 3c54b4d8754f
audit is a skill published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 7,960 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…