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-chartgit 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-chart)<a href="https://agentmods.dev/skills/torvaldz/trailhead/trailhead-chart"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-chart/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-chart"><img src="https://agentmods.dev/badge/skills/torvaldz/trailhead/trailhead-chart.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.00138 | $0.02118 |
| Opus 5.5 | $0.00055 | $0.00847 |
| Sonnet 5.5 | $0.00028 | $0.00424 |
| Haiku 4.5 | $0.00014 | $0.00212 |
Grade A, and why
trailhead-chart 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trailhead-chart is the chart cluster of the trailhead skill: the verbs that give a map its start or bring outside work into it. new charts a new map from a loose idea; adopt maps an existing codebase into a map; ticket opens a ticket of any type on the fly; inbox triages issues opened by others; grill runs a standalone grilling session. 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.
Routing: verb to engine
The first word of the arguments is the verb; the rest is the text (a loose idea, a <type> <title>, an issue number, or a topic).
new/adopttoreferences/charting.md: how a map is born (Mode 1 and Mode 1-bis). Read that file.ticket <type> <title>to the Open a ticket on the fly engine below.inbox [issue]toreferences/inbox.md: the triage protocol. Read that file.grill [topic|ticket]to the Standalone grill engine below.
The cross-cluster situational references and the technique bodies these engines call live in _shared/; this cluster names each by its ../_shared/... path where it needs one (the gh cookbook, the out-of-scope rules, teamwork, the techniques).
What ships with it
2 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.
- 4d ago Changed 9b88af9d0e28
- 10d ago Changed 2a3eeee67941
- 1mo ago Changed c354c9ed8c95
- 1mo ago Changed · +2 lines 6a714cbad113
- 1mo ago Changed · -9 lines 13753d0800e2
- 1mo ago First seen · 53 lines · 138 tokens per session scan A 8d94490c7ff5
trailhead-chart is a skill published in the GitHub repository ToRvaLDz/trailhead (30 stars, last pushed 2d ago), licensed MIT. It adds 138 tokens to every session and 2,118 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.