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/quickgit 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.00019 | $0.00241 |
| Opus 5 | $0.00010 | $0.00120 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
quick 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 yesterday.
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 quick action: call the Skill tool with skill name trailhead-work and arguments quick $ARGUMENTS, then carry out the skill's instructions for that verb (open a trailhead:whiteboard ticket from the "text", or take the existing ticket you name, then run the full engine on it without splitting and without map book-keeping). Do not re-implement the behaviour here. The skill is the single source of truth.
When quick "<text>" opens a NEW whiteboard ticket, refresh the pinned trailhead:dashboard right after the ticket exists (a structural event: the whiteboard has no native progress bar, so the dashboard is the only place the ticket shows). This is a required step of the create path, not optional; do not skip it. quick <n> on an existing map ticket does not refresh. See the skill's quick section and the dashboard freshness rule.
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.
- yesterday First seen · 9 lines · 19 tokens per session scan A 04bfccebd6d0
quick is a command published in the GitHub repository ToRvaLDz/trailhead (1 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 241 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
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
doctor
Run procedural readiness checks for goal-flight.
vitaecontext-vitaegraph
Create, validate, index, or use a private VitaeGraph.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
elite-review
Run an elite, high-scrutiny Claude review against the current git workspace.
stop
Deactivate Agentic Loop for this conversation and safely checkpoint unfinished work.