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/obsfx/trekker-claude-code/listgit clone --depth 1 https://github.com/obsfx/trekker-claude-codeWhat 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.00009 | $0.00567 |
| Opus 5 | $0.00005 | $0.00283 |
| Sonnet 5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
trekker:list 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List and explore tasks with powerful filtering and sorting for situational awareness.
IMPORTANT: /trekker:list is a skill (invoke via Skill tool), NOT a bash command. Use trekker list or trekker task list CLI as shown below.
Two List Commands
trekker list- Unified view across epics, tasks, and subtaskstrekker task list- Tasks only
Common Patterns
Session Start (MANDATORY Context Recovery)
Always gather context via CLI before working:
# 1. SEARCH for what you're working on
trekker search "<topic/area>"
# 2. Review recent activity
trekker history --limit 10
# 3. All active work, prioritized
trekker list --status todo,in_progress --sort priority:asc
# 4. What's currently being worked on?
trekker --toon task list --status in_progress
Finding Work to Do
# Ready tasks by priority
trekker list --type task --status todo --sort priority:asc
# Critical and high priority items
trekker list --priority 0,1 --sort priority:asc
Project Overview
# Everything (all types, all statuses)
trekker list
# Recent items first
trekker list --sort created:desc --limit 20
# Alphabetical for scanning
trekker list --sort title:asc
Filtered Views
# By status
trekker --toon task list --status <status>
# By epic
trekker --toon task list --epic <epic-id>
# By type
trekker list --type task,subtask --status todo
# Combined filters
trekker list --type task --status in_progress --priority 0,1,2
Filter Options
| Filter | Values |
|---|---|
--type |
task, subtask, epic |
--status |
todo, in_progress, completed, wont_fix, archived |
--priority |
0 (critical) to 5 (someday) |
--sort |
priority:asc, created:desc, title:asc |
Output
Use --toon flag for token-efficient output when listing many tasks.
After Listing
- If in_progress tasks found: verify you should continue or update status
- If many todo tasks: consider prioritizing with
trekker task update <id> -p <priority> - If stale tasks: review and update or archive
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 · 89 lines · 9 tokens per session scan A bb1038592178
trekker:list is a command published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 567 once invoked, about $0.0000 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
handoff
Declare that another repo needs corresponding development: write a handoff (+ decision + conversation) into the workspace root scv repo. Multi-repo (nested) only. Use whenever work in this repo implies a change another repo must make — not only when they type /scv:handoff. Never leave that dependency in prose; this…
status
Show raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
report
Post a phase/status report to the team channel per REPORTING.md. Reads .env NOTIFIERPROVIDER (slack|discord) and uploads E2E artifacts from test-results/. Use whenever the user asks to tell the team, post an update, or share progress — not only when they type /scv:report. Never compose the message by hand; this one…
triage
Move tracker issues and external PRs through the triage state machine into agent-ready briefs. Use when triaging incoming issues, an external PR, or the backlog. Reads the tracker + label config written by /orc:setup.
wayfinder
Plan a chunk of work too big for one session as a shared map of decision tickets on the configured tracker; each session resolves exactly one decision. Use when an effort spans many sessions and the route isn't visible yet; /orc:plan covers single-session planning, orc:to-issues slices a settled plan.