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-prompt-packgit 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-prompt-pack)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/vibeflow-prompt-pack"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-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/vibeflow-prompt-pack"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-prompt-pack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 33 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00052 | $0.01048 |
| Opus 5 | $0.00026 | $0.00524 |
| Sonnet 5 | $0.00010 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
vibeflow-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 12d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeflow: Prompt Pack
Build a self-contained prompt pack from a spec, for a coding agent that has no
context beyond the prompt itself. Real patterns from .vibeflow/ go in it.
Usage: Provide the spec file path or feature name as input.
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.
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 run the vibeflow-gen-spec skill again 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.
2. Anti-scope
What not to do, from the spec.
3. Budget
Max files to change — the budget resolved in step 0.
4. Project patterns to follow
What decides whether the pack works. Copy the relevant sections of
.vibeflow/patterns/*.md and .vibeflow/conventions.md in full, with their
real code examples — the receiving agent cannot open files you reference.
Format:
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.
- 12d ago First seen · 115 lines · 52 tokens per session scan A 2773954c4e78
vibeflow-prompt-pack is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 1,048 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
copilot-setup-audit
Audit repository Copilot customization setup. Use this skill to analyze existing configuration, identify missing files, check for best practices, and suggest improvements for agents, prompts, instructions, and skills.
copilot-compatibility-checker
Check VS Code and GitHub Copilot feature compatibility. Use this skill when diagnosing why a feature isn't working, checking required settings, or verifying version requirements for experimental features.
copilot-skill-builder
Create and maintain Agent Skills for VS Code and GitHub Copilot. Use this skill when setting up new skills, skill directories, or SKILL.md files. Helps scaffold project skills in .github/skills/ or personal skills in /.copilot/skills/.
personetta-set-active
Switches the active Personetta persona via set-active. The target tool is auto-detected from the host agent (Claude Code here), so no --format is needed. Use when the user asks to change recipe, switch persona, or set active role.
personetta-current
Reports the active Personetta recipe id using the installed CLI. The host agent (Claude Code here) is auto-detected. Use when the user asks for their current persona, active recipe, or which Personetta role is on.
personetta-list
Lists Personetta recipes (and optionally roles) using the installed Personetta CLI. Use when the user asks what recipes or personas exist before switching.