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/quicknpx skills add pe-menezes/vibeflow --skill 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/quick)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/quick"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/quick.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 | $0.00050 | $0.01144 |
| Opus 5 | $0.00025 | $0.00572 |
| Sonnet 5 | $0.00010 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description and examples
What it does: For small, well-defined tasks (e.g. tiny feature, small planned change), skips PRD and full spec: generates a minimal spec in memory and a prompt pack you can hand to the coding agent. Task should fit in ≤4 files.
Examples:
/vibeflow:quick corrigir formatação de data no dashboard— One command; you get a prompt pack and can paste it to the agent./vibeflow:quick adicionar botão de exportar CSV na tela de relatórios— Same; use when scope is clear and small.
Language
Detect the language of the user's input ($ARGUMENTS or conversation). Write ALL output in that same language. Technical terms in English are acceptable regardless of 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.
Fast-track prompt pack for: $ARGUMENTS
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
/vibeflow:hotfix. - The idea is vague → use
/vibeflow:discoverfirst. - You need full documentation for the team → use the full pipeline.
- The task is large or architecturally significant → use
/vibeflow:gen-spec.
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, or.cursor/rules/, if present, for conventions.
Findings stay in memory. At the end, suggest: "For deeper analysis, run
/vibeflow:analyze."
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.
- 4d ago First seen · 114 lines · 50 tokens per session scan A 8dd7c6224c52
quick is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 1,144 once invoked, about $0.0003 per session on Opus 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
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…
docs-impact-architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume /…
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".
prompt-of-the-week
Generates a weekly PowerPoint slide from a PnP copilot-prompts GitHub sample URL (for example, samples/agent-instructions/creator-agent), derives the correct weekly title from the sample folder, and produces a styled .pptx file that matches the Prompt-K template layout.
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…