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/history)<a href="https://agentmods.dev/commands/obsfx/trekker/history"><img src="https://agentmods.dev/badge/commands/obsfx/trekker/history/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/history"><img src="https://agentmods.dev/badge/commands/obsfx/trekker/history.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.00017 | $0.00491 |
| Opus 5.5 | $0.00007 | $0.00196 |
| Sonnet 5.5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
trekker:history 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:history — 100% identical, 0 lines differ
What it actually says
View the audit trail of all changes (creates, updates, deletes) to recover context from past sessions.
IMPORTANT: /trekker:history is a skill (invoke via Skill tool), NOT a bash command. Use trekker history CLI as shown below.
Why Use History
- Session start: Understand what happened since you last worked
- Before modifying: See who changed what and when
- Conflict debugging: Track down when/how something changed
- Context recovery: Remember decisions from previous sessions
Arguments
$1: Entity ID (optional, e.g., TREK-1) - filter to specific entity
Execution
# Default: Recent changes across all entities
trekker history --limit 15
# For specific entity (if ID provided)
trekker history --entity <entity-id>
# For session context (combine with filters)
trekker history --type task --action update --limit 20
Common Patterns
Session Start Context Recovery
# What happened recently?
trekker history --limit 15
# Focus on task changes
trekker history --type task --limit 10
Before Modifying a Task
# See change history for this task
trekker history --entity TREK-1
Understanding Recent Activity
# Only creates (new items)
trekker history --action create --limit 10
# Only updates (status changes, edits)
trekker history --action update --limit 10
# Changes since a date
trekker history --since 2025-01-15
Output Interpretation
Each history entry shows:
- Timestamp: When the change occurred
- Entity: Which task/epic/subtask was affected
- Action: create, update, or delete
- Changes: What specifically changed (for updates)
After Viewing
If history reveals:
- Stale in_progress tasks: Check if they should be completed or updated
- Recent completions: Review comments for context on what was done
- Conflicts: Use
trekker task show <id>to see current state
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 · 77 lines · 17 tokens per session scan A 79139e344089
trekker:history is a command published in the GitHub repository obsfx/trekker (84 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 491 once invoked, about $0.0001 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.