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-viewgit 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-view)<a href="https://agentmods.dev/skills/torvaldz/trailhead/trailhead-view"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-view.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.1 | $0.00116 | $0.03753 |
| Opus 5 | $0.00058 | $0.01877 |
| Sonnet 5 | $0.00023 | $0.00751 |
| Haiku 4.5 | $0.00012 | $0.00375 |
Grade A, and why
trailhead-view 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trailhead-view is the view cluster of the trailhead skill: the read-only renders of the trailhead surface. map renders the low-res map (destination, decisions, frontier, fog); dashboard regenerates and shows the pinned per-repo index of every open map plus the whiteboard; whiteboard renders the loose, map-less tickets. These verbs present state; they change nothing on the tracker, except: the dashboard's create-and-pin self-heal, and a user-confirmed map close (the map render's exhaustion check for the map it renders, and the dashboard render / self-heal advisory's offer to close any other exhausted-but-open map). Everything lives on the GitHub Issues; the repo holds code only.
Load first, in order
Before doing anything, read ../_shared/load-first.md and follow it: the shared-core load contract (the six core files, in order, then the effective config). _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.
These are read-only renders: no isolation workspace is set up.
Routing: verb to engine
The first word of the arguments is the verb; the rest is an optional map selector.
map [map]to the Render the map engine below.dashboardto the Render the dashboard engine below.whiteboardto the Render the whiteboard engine below.
The cross-cluster situational references these renders call live in _shared/; this cluster names each by its ../_shared/... path where it needs one (the gh cookbook for the dashboard commands, the out-of-scope rules). The multi-cluster model, the frontier-order and blocked-by-drift rules, and the handoff are also in _shared/.
Render the map: map [map]
A single trailhead:map issue is the canonical artifact: an index, not a store, listing the decisions made and pointing at the tickets that hold their detail. A decision lives in exactly one place (its ticket); the map gists it and links.
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.
- 3d ago Changed · -7 lines 6afbe01d7105
- 8d ago First seen · 114 lines · 116 tokens per session scan A 3fb8e1dbe4fa
trailhead-view is a skill published in the GitHub repository ToRvaLDz/trailhead (5 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 3,753 once invoked, about $0.0006 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-31.
Other skills, from other repositories
onboard
Interviews someone about a software project as a whole — the problem it solves, who it serves, what is in and out of scope, the hard constraints, and the domain vocabulary — and writes it up as a project constitution that every later feature specification inherits. Use this at the start of a project, before any…
fabrik-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.
fabrik-implement
Use when operating as the Fabrik Implement stage agent. This skill guides the implementation of a planned feature, following the task checklist to produce committed, tested, pushed code on a feature branch.
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…
akidevsync-notes
Read and edit a project's .akidevsync/notes.json task/note file — the per-project task list written by the Aki-Dev-Sync app (github.com/lacvietanh/aki-dev-sync). Use when the user asks to list, add, pin/unpin, mark done, edit, or delete a task in that file, or mentions "task note", "note ghim", "pin task", "mark…
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…