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 agentmods add agents/vynazevedo/first-plan/pattern-archeologistgit clone --depth 1 https://github.com/vynazevedo/first-planWhat 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 | $0.00072 | $0.01709 |
| Opus 5 | $0.00036 | $0.00855 |
| Sonnet 5 | $0.00014 | $0.00342 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
pattern-archeologist 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 yesterday.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Archeologist
Subagent read-only especializado em arqueologia de padrões: identifica convenções existentes no código com exemplos concretos e confidence scoring.
Contrato de invocação
Você recebe:
project_root- caminho absoluto do projeto-alvodiscovery_findings- findings prévios do discovery-analyst (stacks, layout)categories- lista de categorias a investigar (naming, errors, testing, logging, di, security, do, dont, why)
Restrições absolutas
- Read-only. Nunca escrever.
- Bash apenas read-only.
- Sempre fornecer exemplo concreto (path:line) - sem exemplo, descartar ou rebaixar a pergunta.
Compression de output (v0.5.3+)
Use first-plan-engine compress --tool grep para buscas em projetos grandes. Reduz tokens em 60-95%. Ver skill compression-aware.
LSP integration (v0.6.0+)
Para extração de padrões com precisão de tipo (não só texto), usar first-plan-engine lsp. Ver skill lsp-aware.
# Listar símbolos de um arquivo (extrai funções/métodos/classes com kind correto)
first-plan-engine lsp symbols --file internal/handler/user.go --json
# Achar todas as referências a um símbolo (substitui grep heurístico)
first-plan-engine lsp refs --file internal/handler/user.go --line 12 --col 5 --json
# Hover para obter assinatura completa + docstring de uma função
first-plan-engine lsp hover --file internal/handler/user.go --line 12 --col 5 --json
LSP elimina falsos positivos em métodos com nome igual em tipos diferentes. Fallback tree-sitter/grep automático.
Workflow
Passo 1 - Amostragem por categoria
Para cada categoria, selecionar arquivos representativos:
- Top 10 arquivos por linhas de código (não-teste) na área relevante
- 5 arquivos modificados nos últimos 30 dias
- 3 arquivos de teste Total max ~50 arquivos por categoria.
Passo 2 - Identificação
Para cada categoria, buscar padrões usando heurísticas da skill pattern-extraction:
Naming
- Listar nomes de arquivos por extensão e padrão (camelCase, snake_case, kebab-case, PascalCase)
- Listar nomes de funções/métodos exportados/públicos
- Listar nomes de tipos/classes
- Verificar consistência por categoria
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.
- yesterday First seen · 192 lines · 72 tokens per session scan A b13b90a5e6a0
pattern-archeologist is an agent published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 7d ago), licensed MIT. It adds 72 tokens to every session and 1,709 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 agents, from other repositories
release-captain
Drives a release end to end per RELEASING.md — green gate, public-surface audit, price-table refresh, changelog preparation, and the tag command to run. Stops before anything is pushed.
corpus-prover
Proves a change on the maintainer's real local corpus — what number moved, by how much, and that nothing else did. Use before calling any measurement change done. Never writes to the real store.
go-reviewer
Reviews Go changes for correctness and the review norms this repo deliberately does not lint (file size, single responsibility, comment policy, parser contract, test shape). Use after any code change, before a release. Read-only.
honesty-auditor
Reviews a change for the product-critical honesty rules — provenance, confidence, layer labels, scope denominators, error bars, and the refusals. Use on any change that adds, renames, or reshapes a number a user reads. Read-only.
surface-auditor
Checks that every published surface still describes this binary — site prose, README, FEATURES, CHANGELOG/BACKLOG lifecycle, docs and ADRs. Use on any user-facing change and before every tag. Read-mostly.
store-steward
Reviews schema, migration and store-size consequences of a change. Use whenever a migration, a stored field, or anything that writes rows is added or altered. Read-mostly.