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.00107 | $0.00590 |
| Opus 5 | $0.00053 | $0.00295 |
| Sonnet 5 | $0.00021 | $0.00118 |
| Haiku 4.5 | $0.00011 | $0.00059 |
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 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
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. 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 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 or update); the rest is that verb's argument (get, set <key> <value>, 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.
The full config key reference is a single source, shared with the rest of the skill: ../_shared/configuration-reference.md (keys + guided setup).
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.
- 4d ago Changed · -7 lines f0f1a6f90dfd
- 9d ago First seen · 31 lines · 107 tokens per session scan A 1d1927be41da
trailhead-manage is a skill published in the GitHub repository ToRvaLDz/trailhead (5 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 590 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-31.
Other skills, from other repositories
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.
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.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.