vd-help

A user-invoked help command for the VibeDev project workflow. It examines the current project situation and suggests the next concrete command.

In plain words
What is it for?
Use it when you are lost, do not know the next step, or are unsure which VibeDev command fits your current work.
Why use it?
It helps when you are unsure which of the project's commands to use next. It maps common situations such as starting, building, checking, launching, or closing a project.

Command

Install

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.

agentmods
npx agentmods add commands/4pixeltechbr/vibedev/vd-help
Clone the repo
git clone --depth 1 https://github.com/4pixeltechBR/VibeDev
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01219
Opus 5 $0.00000 $0.00609
Sonnet 5 $0.00000 $0.00244
Haiku 4.5 $0.00000 $0.00122

Measured 2d ago against content hash 24acaf24848a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vd-help 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 2d 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.

vibedev/commands/vd-help.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/vd-help

Router do VibeDev. Use quando você tá perdido, não sabe qual comando chamar, ou o framework te deixou confuso.

Tipo de invocação

User-invoked. Só humano chama. Não dispara automaticamente.

Inspirado por ask-matt em mattpocock/skills (referência competitiva, ver CREDITS.md), mas adaptado pra leigo.

O que é

Você tem 12 comandos. Não precisa decorar todos. O /vd-help olha onde você tá no projeto e sugere o próximo passo concreto.

Nota: o 12º comando é /vd-arch-review — auditoria arquitetural pra devs. Leigos podem ignorar.

Mapa mental — o ciclo normal

1. Tô começando do zero?
   → /vd-spark (extrai a ideia em 4 rodadas)
   → /vd-start (cria o projeto)
   → /vd-status (vê onde tá)

2. Tô no meio do projeto
   → /vd-status (orienta)
   → /vd-plan (planeja próxima coisa)
   → /vd-build (executa)
   → /vd-check (valida se funcionou)

3. Tô em dúvida se o que fiz tá bom
   → /vd-check (valida explicitamente)

4. Tô travado há dias / sem energia
   → /vd-kill (encerra com dignidade, salva aprendizado)

5. Tô lançando (gate Fase 7→8)
   → /vd-launch (blocos de comunicação + checklist)

6. Tô encerrando a sessão de hoje
   → /vd-close (atualiza estado + post-mortem)

Mapa mental — pelas fases

Fase Comando principal Quando sai
1 — Validação /vd-spark/vd-start/vd-status Quando tem 1 frase clara do problema
2 — Especificação /vd-plan Quando tem lista de features + anti-escopo
3 — Arquitetura /vd-plan (com tabela de custo) Quando tem stack + custo estimado
4 — Segurança (embutida em 6) Quando auth/dados estão prontos
5 — Versão (embutida em 6) Quando tem git + estrutura
6 — Construção /vd-build + /vd-check Quando sub-tarefas passam no /vd-check
7 — Homologação /vd-check (rodar pra cada feature) Quando usuário real completa o fluxo
8 — Operação /vd-launch → monitoramento Quando tá no ar e estável

Read the full file on GitHub · 120 lines

Changes

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.

  1. 2d ago First seen · 120 lines · 0 tokens per session scan A 24acaf24848a

Subscribe to this mod's changes

vd-help is a command published in the GitHub repository 4pixeltechBR/VibeDev (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,219 tokens. 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.