Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vynazevedo/first-plan/plugin install fpWrote 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/vynazevedo/first-plan/plan-emission)<a href="https://agentmods.dev/skills/vynazevedo/first-plan/plan-emission"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/plan-emission.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.00071 | $0.01214 |
| Opus 5 | $0.00036 | $0.00607 |
| Sonnet 5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
first-plan-plan-emission 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 6d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Emission
Como gerar o plano da Fase 2 que pausa para aprovação humana.
Pré-requisitos antes de gerar plano
.first-plan/existe eSTATE.mdindica fase >=discovered- Stale check: se
08-meta/coverage.mdlista muitos arquivos stale, recomendar/fp:refreshantes - Feature solicitada (texto livre do usuário)
Workflow
Passo 1 - Verificar duplicidade
Antes de qualquer coisa, consultar 09-features/INDEX.md:
- A feature solicitada bate com alguma feature existente lá?
- Se sim, qual o
statusdela?IMPLEMENTED-> Avisar usuário e perguntar: "Esta feature ja consta como implementada em <evidência>. Você quer A) revalidar a implementação, B) modificar a feature existente, C) seguir mesmo assim (a matriz pode estar errada)?"IN_PROGRESS-> Avisar sobre branch/PR ativo. Sugerir continuar nele em vez de começar do zero.DRIFTED-> Sinalizar drift e perguntar se a feature solicitada é justamente reconciliar.SPEC_ONLYouNOT_STARTED-> Prosseguir.
Se nao bate com nenhuma: prosseguir, mas avisar que isto vai virar feature nova em 09-features/.
Passo 2 - Verificar in-flight
Consultar 07-state/in-flight.md:
- Algum branch ou PR aberto toca arquivos que provavelmente serão modificados pela feature?
- Se sim, listar no plano em "Riscos e ambiguidades" e recomendar coordenação.
Passo 3 - Identificar reuse aplicável
Consultar 03-reuse/INDEX.md:
- Por categoria (validação, http, persistência, etc), buscar componentes que se aplicam à feature
- Listar os candidatos no plano com path e justificativa
Passo 4 - Mapeamento concreto
Para cada arquivo:
- Criar: caminho exato + justificativa de criação do zero (se nao tem precedente)
- Modificar: caminho + descrição conceitual da mudança + linhas afetadas se possível
Ordenação:
- Tipos / contratos primeiro
- Lógica de domínio
- Camada de persistência
- Handlers / pontos de entrada
- Testes (mas pode ser intercalado se o projeto faz TDD)
Passo 5 - Aderência aos padrões
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.
- 6d ago First seen · 127 lines · 71 tokens per session scan A 3a9721bda845
first-plan-plan-emission is a skill published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 1,214 once invoked, about $0.0004 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
agent-memory
Persistent memory system for AI coding agents. Use when you need to save facts about the user, store interaction preferences, log session events, or search previously saved memories. Triggers on remembering, saving context, recalling past decisions, or when the user says "remember this". Also use proactively when the…
snip
You are an expert at writing declarative YAML filters for snip, a CLI proxy that reduces LLM token consumption by filtering shell output.
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
arch-check
架构与实现审查 —— 基于「概念建模 → 职责划分 → 机制/策略分离 → 因果与不变量 → 属性建模 → 模块化 → SOLID → GRASP → YAGNI」的全维度审查，带置信度门控与假阳性抑制（对抗"过度工程建议"这类 AI slop）。触发于：要求 review/审查架构、检查目录结构/依赖关系/职责划分、重构前评估、技术债盘点、判断是否过度设计，或问「这个设计合理吗 / 该怎么拆 / 有没有循环依赖 / 这个改动架构上 OK 吗」。一律按最高强度审查。用法：arch-check [范围] [--fix|--plan]。范围可为目录/文件/PR；缺省审当前分支相对基线的全部变更。.
Agent Context File Writer
Writes a high-quality CLAUDE.md, .cursorrules, or .windsurfrules file that gives a coding agent the right project context, conventions, and constraints to work effectively.
e2e
Selects and runs the appropriate AgentsMesh end-to-end suite for Web, Desktop, MCP, or iOS, including worktree-specific environment setup and browser-level verification. Use when a change needs E2E coverage, a user asks to execute or diagnose an E2E test, or a cross-service workflow must be verified against the real…