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-claude --skill quickgit clone --depth 1 https://github.com/pe-menezes/vibeflow-claudeWrote 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-claude/quick)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow-claude/quick"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/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.1 | $0.00050 | $0.01081 |
| Opus 5 | $0.00025 | $0.00541 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
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 yesterday.
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
88% identical to quick — 0 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 — 113 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:
quick corrigir formatação de data no dashboard— One command; you get a prompt pack and can paste it to the agent.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 current request 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 the prompt pack requested by the user.
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
hotfix. - The idea is vague → use
discoverfirst. - You need full documentation for the team → use the full pipeline.
- The task is large or architecturally significant → use
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
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.
- yesterday Changed · -1 lines ec0fceadedeb
- 8d ago First seen · 114 lines · 50 tokens per session scan A 8dd7c6224c52
quick is a skill published in the GitHub repository pe-menezes/vibeflow-claude (2 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,081 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to quick, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…