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 OpenOps-Studio/vibe-driven-dev --skill codebase-auditorgit clone --depth 1 https://github.com/OpenOps-Studio/vibe-driven-devWrote 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/openops-studio/vibe-driven-dev/codebase-auditor)<a href="https://agentmods.dev/skills/openops-studio/vibe-driven-dev/codebase-auditor"><img src="https://agentmods.dev/badge/skills/openops-studio/vibe-driven-dev/codebase-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/openops-studio/vibe-driven-dev/codebase-auditor"><img src="https://agentmods.dev/badge/skills/openops-studio/vibe-driven-dev/codebase-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.03361 |
| Opus 5.5 | $0.00027 | $0.01344 |
| Sonnet 5.5 | $0.00014 | $0.00672 |
| Haiku 4.5 | $0.00007 | $0.00336 |
Grade A, and why
codebase-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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
1 file 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 · 496 lines · 68 tokens per session scan A 167b547dbdda
codebase-auditor is a skill published in the GitHub repository OpenOps-Studio/vibe-driven-dev (1 stars, last pushed 6mo ago), with no licence file. It adds 68 tokens to every session and 3,361 once invoked, about $0.0003 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-31.
Other skills, from other repositories
codebase-auditor
Scan a repository against curated coding standards and produce a structured audit report, issue set, refactor plan, and sprint-based remediation roadmap. Use when the user invokes /vibe.audit or asks to review the codebase against established rules. Operates in full autopilot mode from repository scan to sprint plan…
post-prd-expander
Expand a completed PRD into the full execution-readiness artifact package across 3 ordered layers with quality gates, post-PRD skill bootstrapping, and autopilot decision checkpoints.
onboarding-guide
Guide a non-technical user through the first project conversation using Intent Capture Popups, capture minimal intent, translate it into VDD state, and propose the next best step in plain language.
prd-orchestrator
Orchestrate the phased installation and execution of external PRD skills to produce an execution-ready PRD with quality gates between each phase.
bootstrap-writer
Generate the essential project setup files (PRD, Logic, Structure, etc.) that move a project from design completion to a structured repository foundation ready for execution.
decision-ledger
Record, track, and surface major decisions that materially affect the project across all stages — planning, architecture, detail, QA, and handoff.