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 prompt-packgit 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/prompt-pack)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow-claude/prompt-pack"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/prompt-pack/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-claude/prompt-pack"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow-claude/prompt-pack.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.00063 | $0.01173 |
| Opus 5 | $0.00032 | $0.00587 |
| Sonnet 5 | $0.00013 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
prompt-pack 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 5d 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 prompt-pack — 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description and examples
What it does: Reads a spec from .vibeflow/specs/ (or path), builds a single prompt that includes objective, DoD, anti-scope, and real code patterns. Saves to .vibeflow/prompt-packs/<slug>.md. Give that file to the coding agent so it implements without needing the rest of the repo context.
Examples:
prompt-pack .vibeflow/specs/login-flow.md— Generate prompt pack from the login-flow spec.prompt-pack login-flow— Same; agent finds the spec by name.
Language
Write the whole pack — opening line, objective, DoD, anti-scope, guidance — in the user's detected language. Code, paths, and technical names stay in English.
Generate a self-contained prompt pack for the spec in the user's current request.
Steps
- Validate spec size. Read the spec: more than 7 DoD checks, or over the
budget (the spec's Budget field, else the
Suggested budgetline in.vibeflow/index.md, else ≤6 files), and you stop without generating the pack — tell the user it exceeds limits (N checks / N files) and to rungen-specagain to split it first. - Locate the spec: a file path is read directly; a feature description is
matched against
.vibeflow/specs/. No spec exists → generate one in the gen-spec format, save it, then continue. - Read
.vibeflow/conventions.md, plus the pattern docs the spec lists under Applicable Patterns. If it lists none, resolve them: read the## Pattern Registryblock inindex.md(between<!-- vibeflow:patterns:start/end -->markers) and cross-reference its tags and modules against the spec's scope — top 3–5 matches; with no registry, infer which are relevant. - Read the codebase files this task touches, plus anything the spec lists under References.
- Generate the pack.
The pack opens with
You are only seeing this prompt; there is no context outside it.
Then, in this order
1. Objective and Definition of Done
From the spec. Non-negotiable.
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.
- 5d ago Changed · -1 lines · +3 tokens per session ffcb77eefe40
- 12d ago First seen · 130 lines · 60 tokens per session scan A ac83f47068d2
prompt-pack is a skill published in the GitHub repository pe-menezes/vibeflow-claude (2 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 1,173 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to prompt-pack, 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…