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/donegit 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.00010 | $0.00344 |
| Opus 5 | $0.00005 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
trekker:done 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
Mark a task as completed with a summary comment.
IMPORTANT: /trekker:done is a skill (invoke via Skill tool), NOT a bash command. There is no trekker done CLI command. Use trekker task update as shown below.
Arguments
$1: Task ID (e.g., TREK-1) - optional
If no task ID provided:
- Show current in_progress tasks
- Ask which task to complete
CRITICAL: Summary Comment is MANDATORY
Never mark a task complete without a detailed summary comment. Future sessions depend on this context.
Good summary includes:
- What was done (specific changes)
- Which files were modified
- Any decisions made
- Links to related tasks if any
Flow
- Review task history for context:
trekker history --entity <task-id> - Ask for a completion summary (what was done, files changed, decisions made)
- Add detailed summary comment
- Set status to completed
- Show ready tasks to find next work
Execution
# Review task history first
trekker history --entity <task-id>
# Add detailed summary comment (MANDATORY)
trekker comment add <task-id> -a "claude" -c "Summary: <what was done>. Files: <modified files>. Changes: <specific changes>."
# Mark as completed
trekker task update <task-id> -s completed
# ALWAYS show ready tasks after completing work
trekker --toon ready
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 · 51 lines · 10 tokens per session scan A a7bc2c672e50
trekker:done is a command published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 344 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
beans-release-notes
Generate release notes from commits since the last version tag and write them to .docs.local/RELEASE.md.
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
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.
jira-breakdown
Turn a feature brief, PRD, or existing Epic into a full Jira hierarchy behind a preview gate. Use when building out a Jira epic/backlog, breaking a feature into Jira tickets, or enforcing the Epic→Story→Task structure.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.