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 --skill vibeflow-analyzegit 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/vibeflow-analyze)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/vibeflow-analyze"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-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/vibeflow-analyze"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-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.00058 | $0.05901 |
| Opus 5 | $0.00029 | $0.02950 |
| Sonnet 5 | $0.00012 | $0.01180 |
| Haiku 4.5 | $0.00006 | $0.00590 |
Grade C, and why
vibeflow-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 10d 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
88% identical to analyze — 93 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 — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeflow: Analyze
Deep-analyze the current codebase. Discovers stack, architecture,
patterns, conventions, key components, and pitfalls. Creates curated
documentation in .vibeflow/ that persists and can be committed to git.
Supports incremental analysis: if .vibeflow/ already exists, detects
changes via git and updates only affected modules.
Usage: Invoke this skill from the project root. Pass --fresh as input to force a complete rebuild. Pass --scope <path> to deep-dive into a specific module/directory. Pass --interactive to validate and enrich patterns with human feedback before saving. Pass --satellite <url> to analyze a dependency repo and merge only used patterns.
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.
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 the flags in the input (--fresh, --scope <path>, --interactive,
--satellite <url>) and check whether git is available here.
Decision tree:
--satellite <url>→ satellite mode (below); phases 1–5 don't run. Without an existing.vibeflow/index.md, stop: "Run the vibeflow-analyze skill first to establish project context, then use--satelliteto analyze a dependency repo."--scope <path>→ scoped mode (below); phases 1–5 don't run. Without an existing.vibeflow/index.md, stop: "Runanalyzefirst to establish project context, then use--scopeto deep-dive into specific modules."- No
.vibeflow/, or--freshpresent → full analysis, phases 1–5. .vibeflow/exists and no--fresh→ incremental analysis.--interactivecomposes with every mode: it adds Phase 3.5 before saving and changes nothing else about which phases run.
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.
- 10d ago First seen · 545 lines · 58 tokens per session scan C 67446db5fd8a
vibeflow-analyze is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 5,901 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 88% identical to analyze, differing in 93 lines, and is treated as a copy.
Other skills, from other repositories
copilot-setup-audit
Audit repository Copilot customization setup. Use this skill to analyze existing configuration, identify missing files, check for best practices, and suggest improvements for agents, prompts, instructions, and skills.
copilot-compatibility-checker
Check VS Code and GitHub Copilot feature compatibility. Use this skill when diagnosing why a feature isn't working, checking required settings, or verifying version requirements for experimental features.
copilot-skill-builder
Create and maintain Agent Skills for VS Code and GitHub Copilot. Use this skill when setting up new skills, skill directories, or SKILL.md files. Helps scaffold project skills in .github/skills/ or personal skills in /.copilot/skills/.
personetta-set-active
Switches the active Personetta persona via set-active. The target tool is auto-detected from the host agent (Claude Code here), so no --format is needed. Use when the user asks to change recipe, switch persona, or set active role.
personetta-current
Reports the active Personetta recipe id using the installed CLI. The host agent (Claude Code here) is auto-detected. Use when the user asks for their current persona, active recipe, or which Personetta role is on.
personetta-list
Lists Personetta recipes (and optionally roles) using the installed Personetta CLI. Use when the user asks what recipes or personas exist before switching.