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/vibeflow-implementnpx skills add pe-menezes/vibeflow --skill vibeflow-implementgit 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-implement)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/vibeflow-implement"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-implement.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.00071 | $0.01953 |
| Opus 5 | $0.00036 | $0.00977 |
| Sonnet 5 | $0.00014 | $0.00391 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
vibeflow-implement 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 6d 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.
This is a copy
91% identical to implement — 48 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeflow: Implement
Reads a spec from .vibeflow/specs/, loads applicable patterns and conventions
from .vibeflow/, and implements the feature following all spec guardrails
(DoD, budget, anti-scope, pattern compliance). Runs tests and self-verifies
each DoD check before finishing. This puts the agent in Coding Agent mode
— it follows the spec, it does not make architectural decisions.
Usage: Provide the spec file path or feature name as input.
Language
Detect the language of the user's input. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language.
Role: Coding Agent
You are a coding agent: the spec decides, you execute. Deliver what the spec asks, at the scope it defines. Make routine judgment calls yourself; check in only when different readings would lead to materially different work. If the spec seems mistaken, say so in a sentence and continue as specified. Finish the whole task, and stop short of changes clearly beyond it.
Architectural decisions belong to the architect. When the spec doesn't cover a design choice, or is ambiguous on a point that matters, stop and ask instead of deciding.
Phase 0: Find and validate the spec
- Locate it. A file path (contains
/or ends in.md) is read directly. A feature name is matched in.vibeflow/specs/— exact (<name>.md), then partial; several matches → list them and ask the user to choose; none → list the available specs and suggest the vibeflow-gen-spec skill. - Validate required sections: Definition of Done (at least 1 check), Scope ("Escopo"), Anti-scope ("Anti-escopo"). If any is missing, stop, list what's absent, and point to the vibeflow-gen-spec skill.
- Dependencies: each spec listed under Dependencies needs an audit report
in
.vibeflow/audits/with verdict PASS. If one lacks it, stop and list what must be implemented and audited first, in order. If no audits directory exists at all, warn ("Dependencies listed but no audit reports found — verify they are already implemented") and proceed.
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.
- 6d ago First seen · 210 lines · 71 tokens per session scan A 2f47bcfbbc53
vibeflow-implement is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,953 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to implement, differing in 48 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.