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-quickgit 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-quick)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/vibeflow-quick"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-quick/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-quick"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-quick.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00964 |
| Opus 5.5 | $0.00025 | $0.00386 |
| Sonnet 5.5 | $0.00013 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
vibeflow-quick 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeflow: Quick
Fast-track: generate a prompt pack for small tasks in one command. Skips discover, generates ephemeral spec, outputs ready-to-use prompt pack.
Usage: Provide the task description 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.
When to use
Small planned tasks and features with clear requirements, fitting in ≤4 files, when you want a prompt pack now rather than a paper trail. Not for:
- An observed defect with reproducible evidence → use the vibeflow-hotfix skill.
- The idea is vague → use the vibeflow-discover skill first.
- You need full documentation for the team → use the full pipeline.
- The task is large or architecturally significant → use the vibeflow-gen-spec skill.
Phase 0: Check context
.vibeflow/ exists → skip to Phase 2 and use it. Otherwise → Phase 1.
Phase 1: Lightweight scan (only without .vibeflow/)
Enough to understand the project, and no more — this doesn't generate
.vibeflow/ and writes nothing to disk:
- The project's config files, for the stack.
- The top 2 directory levels, for the structural units.
- Three or four key files: the entry point, one route or handler, one model or type definition, one test (if present).
.cursorrules,CLAUDE.md,.github/copilot-instructions.md, or.cursor/rules/, if present, for conventions.
Findings stay in memory. At the end, suggest: "For deeper analysis, run the vibeflow-analyze skill."
Phase 2: Generate the ephemeral spec
From .vibeflow/ or the Phase 1 context, build a spec in memory only —
never saved to a file — containing:
- Objective — 1 sentence. What changes for the user.
- Definition of Done — 3-5 binary checks (fewer than a standard spec).
- Scope — What's in. Keep it tight.
- Anti-scope — What's explicitly out. Be aggressive.
- Budget — ≤4 files, tighter than the standard ≤6. A task that clearly needs more gets a warning in the user's language: "This task may be too large for quick. Consider using the vibeflow-gen-spec skill."
- Applicable Patterns — from
.vibeflow/patterns/, when it exists.
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 · 97 lines · 63 tokens per session scan A 26cdd747eae0
vibeflow-quick is a skill published in the GitHub repository pe-menezes/vibeflow (32 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 964 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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.
review
WCAG 2.2 AA curated accessibility review — distinguishes automatically detectable, browser-assisted, and manual/human-judgment findings with evidence citations and SC mapping. Composes with design-assessment/design-improvement/frontend-design-review.