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 analyzegit 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/analyze)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow-claude/analyze"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/analyze/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/analyze"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/analyze.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.00081 | $0.06361 |
| Opus 5 | $0.00041 | $0.03180 |
| Sonnet 5 | $0.00016 | $0.01272 |
| Haiku 4.5 | $0.00008 | $0.00636 |
Grade C, and why
analyze scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Remove the temp directory (`rm -rf <temp_dir>`) whether the merge succeeded or This is a copy
95% identical to analyze — 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 — 596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description and examples
What it does: Scans the codebase and generates (or updates) .vibeflow/: index, conventions, and one pattern doc per significant pattern. Use once for project setup, then after big changes or to deep-dive into a module.
Examples:
analyze— First run or incremental (only re-analyzes what changed since last run).analyze --fresh— Rebuild everything from scratch; ignore existing.vibeflow/.analyze --scope src/app— Deep-dive intosrc/apponly; requires.vibeflow/to already exist. Enriches pattern docs with examples from that module.analyze --interactive— Run analysis with interactive review: validate patterns, remove false positives, add tribal knowledge before saving.analyze --fresh --interactive— Full rebuild with interactive review.analyze --satellite https://github.com/org/design-system— Analyze a dependency repo, keep only patterns your code uses, merge into.vibeflow/patterns/satellite-<name>/.
Language
Detect the language of the user's conversation context.
Write ALL output in that same language.
Technical terms in English are acceptable regardless of the detected language.
Section names in generated .vibeflow/ files may be in English (they are technical),
but all descriptive text, analyses, observations, and final user reports should be
in the detected language.
Web Search Policy
Use WebSearch and WebFetch only when local context (.vibeflow/, codebase,
git history) is insufficient — an unfamiliar framework or API. Local first.
Perform a deep, adaptive analysis of this codebase. The goal is curated pattern documentation that every future spec, prompt pack, and audit uses to keep implementations on the project's real conventions.
Phase 0: Detect mode
Read .vibeflow/index.md directly by its path. Search, grep, and glob respect
.gitignore, so they miss the directory and report it as absent.
Then read any flags in the user's current request (--fresh, --scope <path>, --interactive,
--satellite <url>) and check whether git is available here.
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 · +5 lines 2c41432a0534
- 9d ago First seen · 591 lines · 81 tokens per session scan C e0df157e585e
analyze is a skill published in the GitHub repository pe-menezes/vibeflow-claude (2 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 6,361 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 95% identical to analyze, 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.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…