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-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/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-implement"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-implement.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.00071 | $0.01953 |
| Opus 5.5 | $0.00028 | $0.00781 |
| Sonnet 5.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 1mo 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 — 47 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.
- 1mo 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 (32 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,953 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to implement, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
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".
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
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.
design-improvement
WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.
codeql
CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.
confluence-permission
Manage space and page permissions and restrictions. ALWAYS use when user wants to control access, set restrictions, or manage who can view/edit content.