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 pe-menezes/vibeflow-claude --skill auditgit clone --depth 1 https://github.com/pe-menezes/vibeflow-claudeWrote 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/pe-menezes/vibeflow-claude/audit)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow-claude/audit"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/audit/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/pe-menezes/vibeflow-claude/audit"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/audit.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.00093 | $0.03438 |
| Opus 5 | $0.00046 | $0.01719 |
| Sonnet 5 | $0.00019 | $0.00688 |
| Haiku 4.5 | $0.00009 | $0.00344 |
Grade A, and why
audit scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| SEC108 | WARNING | a | dynamic exec (`eval`/`exec`/`system`/`popen`/`subprocess.call`/`child_process.exec`) | This is a copy
95% identical to audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description and examples
What it does: Finds the spec (in .vibeflow/specs/ or by path), checks each DoD item and pattern compliance, runs the project's test suite, and reports PASS / PARTIAL / FAIL. If tests fail, the result is FAIL regardless of DoD.
Examples:
audit .vibeflow/specs/login-flow.md— Audit implementation against the login-flow spec.audit login-flow— Same; the agent looks up the spec by feature name.
Language
Detect the language of the user's current request or conversation. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language.
Audit the implementation identified in the user's current request.
Steps
With --consolidate-hotfixes in the input, the round's target is
.vibeflow/hotfixes/ instead of a spec — jump to Consolidation mode below.
- Find the spec — in
.vibeflow/specs/or at the given path — and extract its Definition of Done. - Read
.vibeflow/conventions.mdand the pattern docs the spec lists under Applicable Patterns. If it lists none, resolve them: read the## Pattern Registryblock inindex.md(between<!-- vibeflow:patterns:start/end -->markers) and cross-reference its tags and modules against the spec's scope — top 3–5 matches; with no registry, infer which are relevant. - Read the codebase files that were supposed to change.
- Run the tests. Prefer commands listed in the spec; otherwise detect the
project's runner from the stack (
.vibeflow/index.md, then test scripts in package.json, pyproject.toml, Cargo.toml, go.mod, and equivalents).- Tests fail → the verdict is FAIL and auditing stops; the incremental prompt pack targets the failures first.
- No runner found → warn "No test runner detected. Verify that tests were run manually." and continue.
- Critical Gate — destructive-op safety scan. A deterministic safety net for dangerous changes the DoD never mentions — security regressions and destructive operations that are side effects, not features. Not a style check.
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 Changed · -1 lines 7cfd86117f74
- 9d ago First seen · 279 lines · 93 tokens per session scan A 3482de06bc0d
audit is a skill published in the GitHub repository pe-menezes/vibeflow-claude (2 stars, last pushed 4d ago), licensed MIT. It adds 93 tokens to every session and 3,438 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 95% identical to audit, differing in 0 lines, and is treated as a copy.
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.