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 skills/igoruehara/spec-driven/mapearnpx skills add igoruehara/spec-driven --skill mapeargit clone --depth 1 https://github.com/igoruehara/spec-drivenWrote 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/igoruehara/spec-driven/mapear)<a href="https://agentmods.dev/skills/igoruehara/spec-driven/mapear"><img src="https://agentmods.dev/badge/skills/igoruehara/spec-driven/mapear.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 | $0.00099 | $0.00557 |
| Opus 5 | $0.00049 | $0.00279 |
| Sonnet 5 | $0.00020 | $0.00111 |
| Haiku 4.5 | $0.00010 | $0.00056 |
Grade A, and why
mapear 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 4d 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.
What it actually says
Skill: Mapear o estado atual (as-is)
Produz o retrato de um projeto já em andamento. Primeiro leia o código, depois pergunte
só o que o código não revela. É idempotente: re-rodar atualiza docs/architecture/assessment.md.
Processo
- Mapeamento automático: identifique stack, estrutura de pastas, estilo de arquitetura,
acoplamentos, testes/CI, logs/métricas/tracing. Infira os bounded contexts implícitos a
partir da organização do código. Em repos grandes, delegue a varredura a um subagente de
exploração (ver
docs/engineering/_templates/subagent.template.md) para manter o contexto enxuto. - Insumos externos (se houver): se
/integracoesconectou GitHub/cloud/Confluence (conta validada), use para enriquecer o as-is. Cite a origem. - Entrevista de lacunas (
AskUserQuestion): intenção de negócio e North Star atuais; maiores dores/riscos hoje; termos de domínio que confundem o time; o que NÃO pode quebrar; contexto e tamanho do time. - Gap analysis: compare o as-is com o padrão SDD nos 5 eixos (tech stack, arquitetura, infra, qualidade, observabilidade). Marque risco (baixo/médio/alto).
- Decisões históricas: liste escolhas estruturais já feitas sem registro → viram ADR retroativo (status: aceito, registrando o porquê histórico).
Saídas
docs/architecture/assessment.md(usedocs/architecture/_templates/assessment.template.md).- Lista de ADRs retroativos a criar em
docs/architecture/adr/.
Próximo passo
- Dentro do
/kickoff: devolva o assessment + gaps para alimentar os 5 eixos e o roadmap. - Sozinha: sugira
/roadmap(priorizar as dívidas mapeadas) ou/camada-agentica.
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.
- 4d ago First seen · 33 lines · 99 tokens per session scan A 2f78dd6ad39c
mapear is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 557 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…