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.
git clone --depth 1 https://github.com/obsfx/trekker-claude-codeWrote 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/commands/obsfx/trekker-claude-code/start)<a href="https://agentmods.dev/commands/obsfx/trekker-claude-code/start"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/start/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/commands/obsfx/trekker-claude-code/start"><img src="https://agentmods.dev/badge/commands/obsfx/trekker-claude-code/start.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.00009 | $0.00441 |
| Opus 5.5 | $0.00004 | $0.00176 |
| Sonnet 5.5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
trekker:start 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 1mo 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.
This is a copy
89% identical to trekker:start — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Begin working on a task by setting its status to in_progress.
IMPORTANT: /trekker:start is a skill (invoke via Skill tool), NOT a bash command. There is no trekker start 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
- Show ready tasks (todo status)
- Ask which task to start
Execution
Step 1: Search for Related Work (MANDATORY)
Before starting ANY task, search for related context:
# Search for related past work using keywords from the task
trekker search "<task title keywords>"
trekker search "<related concepts>"
# Check completed tasks that might inform this work
trekker --toon task list --status completed
Why search first:
- Past tasks may contain solutions you need
- Reveals related work and file locations
- Prevents re-doing solved problems
- Prefer continuity over re-implementation
Step 2: Gather Full Context via CLI (MANDATORY)
# Show task details
trekker task show <task-id>
# View change history for this task
trekker history --entity <task-id>
# Get comments for context
trekker comment list <task-id>
# Check dependencies
trekker dep list <task-id>
Why this matters:
- Understand previous work on this task
- See if it was started/stopped before
- Recall decisions and blockers from past sessions
- If context is unclear: STOP → SEARCH MORE → RESUME
Step 3: Start the Task
# Set status to in_progress
trekker task update <task-id> -s in_progress
After Starting
Display a summary including:
- Task title and description
- Key points from history/comments
- Related tasks found via search
- Any dependencies or blockers
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.
- 1mo ago First seen · 76 lines · 9 tokens per session scan A ea768af962a5
trekker:start is a command published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 441 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to trekker:start, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
flow
Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a behaviour-keeping cleanup, a design fork, or "what next"; --auto drives a ready spec unattended (--tick for one hop) and ends with a PILOTVERDICT line; --until=merge…
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
features
Seed or maintain the committed user-POV feature map at .flow/features/.
land
Resolve and squash merge one named, currently authorized pull request.