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/trekkerWrote 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/deps)<a href="https://agentmods.dev/commands/obsfx/trekker/deps"><img src="https://agentmods.dev/badge/commands/obsfx/trekker/deps/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/deps"><img src="https://agentmods.dev/badge/commands/obsfx/trekker/deps.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.00008 | $0.00199 |
| Opus 5.5 | $0.00003 | $0.00080 |
| Sonnet 5.5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
trekker:deps 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- trekker:deps — 100% identical, 0 lines differ
What it actually says
Add, remove, or list dependencies between tasks.
IMPORTANT: /trekker:deps is a skill (invoke via Skill tool), NOT a bash command. Use trekker dep CLI commands as shown below.
Subcommands
Ask the user what they want to do:
- add: Add a dependency (task A depends on task B)
- remove: Remove a dependency
- list: List dependencies for a task
Add Dependency
"TREK-2 depends on TREK-1" means TREK-1 must be completed before TREK-2.
trekker dep add <task-id> <depends-on-task-id>
Remove Dependency
trekker dep remove <task-id> <depends-on-task-id>
List Dependencies
trekker dep list <task-id>
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 · 36 lines · 8 tokens per session scan A 4afcef8e3c75
trekker:deps is a command published in the GitHub repository obsfx/trekker (84 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 199 once invoked, about $0.0000 per session on Opus 5.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-10-25.
Other commands, from other repositories
maintainer-standup
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
answer
A build round is one archon-ship run on the item. Read how it ended and decide what the queue does next: the item is done, the queue continues it with another round, or a maintainer must decide. The next node performs what you declare and reads it back: it pushes commits the round left unpushed, records your decision…
route
Decide whether the build queue launches its next run on this item, and write the brief the run starts from. Triage already decided the route; you keep it thin. The next node performs what you declare: it launches archon-ship with your brief, raises your attention item, or takes an already finished pull request out of…
decide
This run's $INPUTS.stage stage has ended. Decide whether its ending already has a next step, or whether it stops where only a person can take it forward. When it stops, write the attention item that person answers. You read and decide only: the repository, the forge and the tracker stay exactly as you found them. The…
revisit
Intake recorded each item below as blocked: something had to happen first. Work lands in parallel, so a blocker can be resolved, superseded or made irrelevant while its issue is still open, and an item can stay blocked long after it could move. Judge, for each item, whether it still looks blocked now. You don't…
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.