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-managegit 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-manage)<a href="https://agentmods.dev/skills/torvaldz/trailhead/trailhead-manage"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-manage/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-manage"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-manage.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.00148 | $0.01056 |
| Opus 5.5 | $0.00059 | $0.00422 |
| Sonnet 5.5 | $0.00030 | $0.00211 |
| Haiku 4.5 | $0.00015 | $0.00106 |
Grade A, and why
trailhead-manage 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.
How it starts
The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trailhead-manage is the manage cluster of the trailhead skill: the admin verbs that keep a trailhead install healthy. config shows the effective config or changes it (a guided menu, or get / set <key> <value>); update checks for a newer trailhead and installs it where that is safe; prune reclaims a map's native sub-issue slots under GitHub's 100-cap; audit checks closed tickets for regressions against today's code and finds duplicate or groupable open ones. 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.
These admin verbs resolve no ticket and set up no isolation workspace.
Routing: verb to engine
The first word of the arguments is the verb (config, update, prune, or audit); the rest is that verb's argument (get, set <key> <value>, a map, --all, or empty).
config [get|set …]to../_shared/configuration-reference.md: the config keys, their semantics, and the guided menu setup. With no argument it runs the guided setup;config getprints the merged config read-only (project.trailhead/config.jsonover global over defaults, showing which source wins each key);config set <key> <value>writes one key directly (to the project.trailhead/config.json, or to~/.claude/trailhead/config.jsonwith--global). Read that file and follow it.updatetoreferences/updating.md: the update protocol (detect the install channel, compare the installed version with the latest from the matching source, install the newer one where it is safe). Read that file and follow it.prune [map]toreferences/pruning.md: reclaim native sub-issue slots on a map near or at GitHub's 100 sub-issue cap by dropping the edges of closed and orphan tickets and re-adding missing ones, keeping every reference (Parent line, Decisions-so-far pointer, map label). With no argument it prunes the active map. Read that file and follow it.audit [map] [--all]toreferences/auditing.md: audit the closed tickets since the last audit (or all of them with--all) for regressions against the current code (a fast no-agent path for unchanged code), classing each as implemented, unchanged, evolved, implemented wrong, or not implemented, and compare the open tickets for duplicates and groupable clusters; every fix is a proposal applied only on an explicit yes. With no argument it covers every open map plus the whiteboard; with a map it covers that map only. Read that file and follow it.
What ships with it
3 files 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 3ec80814f4c3
- 17d ago Changed · +1 lines · +18 tokens per session e319cb29ac16
- 1mo ago Changed · +1 lines · +23 tokens per session 0db68a99e235
- 1mo ago Changed · -7 lines f0f1a6f90dfd
- 1mo ago First seen · 31 lines · 107 tokens per session scan A 1d1927be41da
trailhead-manage is a skill published in the GitHub repository ToRvaLDz/trailhead (30 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session and 1,056 once invoked, about $0.0006 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
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.
agency-jira-workflow-steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.