features

A command that displays a table comparing planned features with their implementation status and supporting evidence. It can also filter the table to statuses such as implemented, drifted, or phantom.

In plain words
What is it for?
Use it to review the full feature matrix or show only a selected status, including features with detected differences from the specification.
Why use it?
It makes it easier to spot what has been built, what is still planned, and where the code differs from the specification.

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/vynazevedo/first-plan/features
Clone the repo
git clone --depth 1 https://github.com/vynazevedo/first-plan
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 642 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.00029 $0.00642
Opus 5 $0.00015 $0.00321
Sonnet 5 $0.00006 $0.00128
Haiku 4.5 $0.00003 $0.00064

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

Security

Grade A, and why

features 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.

commands/features.md · 95 lines

How it starts

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

/fp:features

Matriz de Spec-Code Reconciliation.

Argumentos

$ARGUMENTS:

  • vazio: tabela completa
  • status:<X>: filtrar por status específico
  • phantom: apenas phantom features
  • drifted: apenas drift detectado

Workflow

Passo 1 - Pre-flight

Verificar .first-plan/09-features/INDEX.md existe.

Passo 2 - Carregar matriz

Ler INDEX.md + frontmatter + tabela.

Passo 3 - Aplicar filtro

Se filtro aplicado, manter apenas linhas que casam.

Passo 4 - Apresentar

Default:

Matriz de features (<total>)

IMPLEMENTED (<a>):
  F1  User Authentication via JWT       conf 0.91  evidência: internal/auth/jwt.go
  F3  Password Reset Flow               conf 0.85  evidência: internal/auth/reset.go
  ... 

IN_PROGRESS (<b>):
  F5  Two-Factor Authentication         conf 0.78  branch: feat/2fa, PR #42
  ...

SPEC_ONLY (<c>):
  F7  CSV Export                         conf 0.92  fonte: JIRA-456
  ...

NOT_STARTED (<d>):
  F9  Audit Log Replay                   conf 0.70  fonte: docs/audit.md
  ...

DRIFTED (<e>) ⚠
  F12 Email Validation                  conf 0.82  drift: regex permissiva vs spec estrita
  ...

ABANDONED (<f>):
  F15 Old Notification Center           conf 0.65  branch obsoleta há 4 meses
  ...

Phantom features ⚠ (<g>):
  F8  Pagination on /users               implementada mas JIRA-234 ainda Open

Detalhes individuais: .first-plan/09-features/<slug>.md

Filtrado:

Features com status=IMPLEMENTED (<count>)

F1  User Authentication via JWT          conf 0.91
    fonte: docs/auth.md
    evidência: internal/auth/jwt.go:1-150 + tests
    detalhes: .first-plan/09-features/user-authentication-jwt.md

F3  Password Reset Flow                  conf 0.85
    ...

Passo 5 - Alertas

Sempre destacar:

  • Phantom features (alerta forte)
  • DRIFTED (alerta médio)
  • IN_PROGRESS sem update há > 30 dias (sinal de abandonment iminente)

Cuidados

  • Se INDEX.md está stale, recomendar /fp:refresh 09-features antes de confiar plenamente.

Read the full file on GitHub · 95 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 · 95 lines · 29 tokens per session scan A 53a9734836ec

Subscribe to this mod's changes

features is a command published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 642 once invoked, about $0.0001 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.