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/tma1-ai/devtap/devtap-get-build-errorsnpx skills add tma1-ai/devtap --skill devtap-get-build-errorsgit clone --depth 1 https://github.com/tma1-ai/devtapWhat 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.00028 | $0.00331 |
| Opus 5 | $0.00014 | $0.00166 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
devtap-get-build-errors 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.
What it actually says
devtap-get-build-errors
Use this skill when the user asks for build errors, latest build output, or an equivalent quick action.
Workflow
- Call
get_build_statusonce. - Call
get_build_errorsonce when any of these is true:- status reports pending output
- user explicitly asks to fetch/check logs now
- user says new build/test/dev output arrived
- If build succeeded, acknowledge briefly (do not repeat output).
- If build failed, provide a concise summary by default:
- source label(s)
- final failure signal (for example exit code or test summary)
- most actionable failing case/file/error line(s)
- Show raw output verbatim only when the user explicitly asks for full/raw/original logs.
- Keep source warnings verbatim (for example, unreachable source warnings).
- After the output (or summary), add one line:
Next action: <what you will do>.
Rules
- Do not fabricate or reinterpret error content.
- Do not call
get_build_errorsrepeatedly in the same turn unless new output is reported. - MCP tool names map to CLI subcommands:
get_build_status->devtap status,get_build_errors->devtap drain. - If MCP tools are unavailable, use
scripts/get_build_errors.shas CLI fallback.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 34 lines · 28 tokens per session scan A 3968018fc739
devtap-get-build-errors is a skill published in the GitHub repository tma1-ai/devtap (13 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 331 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.
Other skills, from other repositories
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.
first-plan-co-change-analysis
Skill que constrói o Co-change Graph - "quando arquivo X muda, qual outro arquivo geralmente muda junto?". Use durante Discovery e em /fp:cochange. Baseado em git history. Detecta arquivos co-dependentes que devem ser editados juntos para evitar PRs incompletos. v0.3.0+ usa engine nativo Rust quando disponível…
first-plan-provenance-tracker
Skill que define o schema de proveniência e o sistema de freshness tracking para findings em .first-plan/. Use durante Discovery e refresh para registrar source (file:line@SHA), TTL, confidence inicial e cadeia de supersedeção. Aplica decay de confidence baseado em idade.
first-plan-git-intelligence
Skill que extrai inteligência do git history - heatmap de atividade, ownership, branches/PRs in-flight. Use durante Discovery e em /fp:hot, /fp:owner, /fp:in-flight. Tudo via comandos git read-only.
first-plan-protocol
Esta skill DEVE ser carregada em qualquer comando do plugin first-plan. Define o protocolo PLAN-FIRST (Discovery -> Plan -> Approval -> Execution -> Report), as 7 regras invioláveis e o comportamento esperado em cada fase. Ative quando o usuário invocar /fp: ou mencionar "first-plan", "context compilation", "discovery…