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 agentmods add commands/torvaldz/trailhead/workgit clone --depth 1 https://github.com/ToRvaLDz/trailheadWhat 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 | $0.00011 | $0.00140 |
| Opus 5 | $0.00005 | $0.00070 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
work 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 2d 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
Invoke the trailhead skill for the work action: call the Skill tool with skill name trailhead-work and arguments work $ARGUMENTS, then carry out the skill's instructions for that verb (under the repo's trailhead:conventions isolation: worktree or clone, work the ticket in its own isolated workspace on a trailhead/t<n> branch, set up at work-start, per the skill's teamwork reference). Do not re-implement the behaviour here. The skill is the single source of truth.
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.
- 2d ago First seen · 7 lines · 11 tokens per session scan A d20a02551fee
work is a command published in the GitHub repository ToRvaLDz/trailhead (1 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 140 once invoked, about $0.0001 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 commands, from other repositories
jira.log
Log a new Jira issue to RHOAIENG with Team (Ambient team) and Component (Agentic) pre-filled.
hatch3r-board-fill
Create epics and issues/work items from todo.md, reorganize the board with dependency analysis, readiness assessment, and implementation ordering. Supports GitHub, Azure DevOps, and GitLab.
status
Summarise what Fabrik is doing right now — board state, in-flight workers, worktrees with uncommitted changes.
init
Initialize goal-flight state for a project.
agree
Manage the running list of agreements — the canonical registry of confirmed decisions.
kb
KB operations — capture, digest, promote, decide, rituals, present, report, roadmap, journeys.