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/pe-menezes/vibeflow/auditnpx skills add pe-menezes/vibeflow --skill auditgit clone --depth 1 https://github.com/pe-menezes/vibeflowWrote 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/audit)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/audit"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/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.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 today.
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`) | Copies of this mod
1 near-identical copy found in the catalogue:
- vibeflow-audit — 89% identical, 41 lines differ
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.
- today Changed · -1 lines 7cfd86117f74
- 6d ago First seen · 279 lines · 93 tokens per session scan A 3482de06bc0d
audit is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed today), 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…
docs-impact-architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume /…
code-review-csharp
Perform structured code reviews of C# source code covering naming conventions, performance, security, readability, and .NET best practices. Trigger phrases include "review this C# code", "check my C# for best practices", "analyze this C# class", "find issues in my C# code".
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.