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/creategit 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.00353 |
| Opus 5 | $0.00005 | $0.00177 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
trekker:create 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
Create a new task in trekker.
IMPORTANT: /trekker:create is a skill (invoke via Skill tool), NOT a bash command. Use trekker task create CLI as shown below.
MANDATORY: Search Before Creating
You MUST search before creating ANY task. This is non-negotiable.
# Search for existing/related issues FIRST
trekker search "<keywords from task title>"
trekker search "<related concepts>"
If search finds related issues:
- Consider updating the existing issue instead of creating a duplicate
- Add a comment to the existing issue if it needs more context
- Only create a new task if truly distinct from existing work
Interactive Flow
- Search for existing issues (MANDATORY - show results to user)
- If no duplicates found, ask for the task title (required)
- Ask for the task type context:
- Is this part of an epic? If so, which one?
- Ask for priority (0-5, default 2)
- Ask for description (STRONGLY encouraged - tasks without context are useless)
- Ask for tags (optional, comma-separated)
Execution
trekker task create -t "<title>" [-d "<description>"] [-p <priority>] [-e <epic-id>] [--tags "<tags>"]
After Creation
Show the created task details and ask if the user wants to:
- Start working on it immediately (set to in_progress)
- Link it to another task as a dependency
- Create a subtask
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 · 47 lines · 10 tokens per session scan A 39b4dc2f0fad
trekker:create 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 353 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.