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 skills add ToRvaLDz/trailhead --skill trailhead-capturegit clone --depth 1 https://github.com/ToRvaLDz/trailheadWrote 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/torvaldz/trailhead/trailhead-capture)<a href="https://agentmods.dev/skills/torvaldz/trailhead/trailhead-capture"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-capture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/torvaldz/trailhead/trailhead-capture"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-capture.svg" alt="Reviewed on agentmods" width="80" 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.00117 | $0.00649 |
| Opus 5.5 | $0.00047 | $0.00260 |
| Sonnet 5.5 | $0.00023 | $0.00130 |
| Haiku 4.5 | $0.00012 | $0.00065 |
Grade A, and why
trailhead-capture 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 11d 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
trailhead-capture is the capture cluster of the trailhead skill: the zero-friction captures that record work without breaking flow. bug captures a bug ticket; todo captures a small build ticket you will do now; idea captures a fog idea; seed captures a trigger-gated seed; note captures a verbatim note. Everything lives on the GitHub Issues; the repo holds code only.
Load first, in order
Before doing anything, load <skill base>/../_shared/load-first.md and follow it: the shared-core load contract (the six core files, in order, then the effective config). <skill base> is this skill's base directory (Claude Code prints it as Base directory for this skill: when the skill loads; on another host, the directory holding this SKILL.md): resolve the path to an absolute path and open it with the Read tool on that absolute path. Never cd into a skills directory and never read a relative path from the shell (a cd compound followed by a read is denied by the search guard). The same rule covers every later ../_shared/... or references/... path in this skill: resolve it against the base directory to an absolute path before reading. _shared/ is a sibling of this cluster's own directory (at ../_shared/), never a child of it; its absence from a listing of the cluster dir is expected, not a missing core.
A capture writes at most one issue; no isolation workspace is set up.
Routing: verb to engine
The first word of the arguments is the verb (bug, todo, idea, seed, or note); the rest is the text (or --of <ticket> <text> for bug).
bug/todo/idea/seed/notetoreferences/capture.md: the full per-verb protocol and the note/idea/seed/todo spectrum. Read that file and follow it.
The cross-cluster situational references and technique bodies these captures call live in _shared/; this cluster names each by its ../_shared/... path where it needs one.
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.
- 11d ago Changed ba56a40e59df
- 1mo ago Changed · -7 lines d8566eec287d
- 1mo ago First seen · 30 lines · 117 tokens per session scan A 0aa86500fa1f
trailhead-capture is a skill published in the GitHub repository ToRvaLDz/trailhead (30 stars, last pushed 2d ago), licensed MIT. It adds 117 tokens to every session and 649 once invoked, about $0.0005 per session on Opus 5.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-31.
Other skills, from other repositories
plan
Use when operating as the Fabrik Plan stage agent. This skill guides the design of an implementation approach, producing a concrete plan with task checklist that the Implement stage will follow.
implement-comment
Use when operating as the Fabrik Implement comment reviewer. This skill guides applying user-requested code changes during implementation, committing and pushing, and updating the task checklist — without signaling stage completion.
fabrik-setup
Bootstrap a project to use Fabrik (the GitHub-Project-driven SDLC pipeline orchestrator that drives Claude Code workers through Specify/Research/Plan/Implement/Review/Validate stages). Use this skill when the user wants to install, set up, initialize, or get started with Fabrik for the first time — especially when…
specify
Use when operating as the Fabrik Specify stage agent. This skill guides the specification and clarification of a feature request, turning a rough backlog issue into a clear, unambiguous spec before technical research begins.
specify-comment
Use when operating as the Fabrik Specify comment reviewer. This skill guides incorporation of user answers into an evolving spec, removing resolved questions and surfacing follow-ups until the spec is complete.
plan-comment
Use when operating as the Fabrik Plan comment reviewer. This skill guides adjustments to the implementation plan in response to user feedback, updating the task checklist and approach decisions — producing updated plan content that the engine writes back to the Plan stage comment.