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 skills add obsfx/trekker-claude-code --skill searchgit 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/skills/obsfx/trekker-claude-code/search)<a href="https://agentmods.dev/skills/obsfx/trekker-claude-code/search"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/search/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/skills/obsfx/trekker-claude-code/search"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/search.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.00014 | $0.00532 |
| Opus 5.5 | $0.00006 | $0.00213 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
search 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 today.
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
100% identical to search — 0 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: Use This First
Search is your PRIMARY tool for gathering context.
Before starting ANY work:
trekker search "<single keyword>"
This finds related past work using FTS5 full-text search.
IMPORTANT: FTS5 is NOT Semantic Search
Trekker uses FTS5 full-text search, NOT semantic/AI search. This means:
- Use single, specific keywords - not phrases or sentences
- Multi-word queries use AND logic -
"fix authentication bug"requires ALL three words present, returning FEWER results - Search multiple times with different keywords for broader coverage
- Pick the most distinctive word from what you're looking for
| BAD (too many words) | GOOD (single keyword) |
|---|---|
trekker search "fix login authentication bug" |
trekker search "authentication" |
trekker search "user cannot access account" |
trekker search "account" |
trekker search "performance optimization slow" |
trekker search "performance" |
trekker search "deployment pipeline issues" |
trekker search "deployment" |
When to Use (ALWAYS)
- Before creating tasks - find existing work
- Before starting work - gather context
- When investigating issues - find related bugs
- When user describes problem - understand history
- When resuming work - recover context
Commands
# Search with a single keyword
trekker search "authentication"
# Try multiple keywords separately for broader coverage
trekker search "login"
trekker search "password"
# Filter by type
trekker search "deployment" --type task
# Filter by status
trekker search "memory" --status todo
# Rebuild index if needed
trekker search "caching" --rebuild-index
Workflow: Before ANY Task Operation
1. SEARCH: trekker search "<single keyword>"
2. BROADEN: Try 2-3 related keywords if first search has no results
3. REVIEW: Check if similar work exists
4. DECIDE: Update existing OR create new
5. SYNC: Mirror to TodoWrite after Trekker
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.
- today Changed · +2 lines · +14 tokens per session 1114f2f4b75c
- 1mo ago First seen · 75 lines · 0 tokens per session scan A 63c4562bdbde
search is a skill published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 532 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to search, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
flow-next-memory-migrate
Migrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.
catchup
Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean. Use when the human returns after a gap, says they can't follow the project anymore, asks what happened or what a term means, or before deciding what to do next when their mental model…
re0-memo
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Use after a build, QA pass, demo, user complaint, or abandoned attempt when the useful output is what the next pass must learn rather than the code itself.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.
recollect
The user vaguely recalls a past discussion, line of work, topic, or settled concept but cannot name it: find it in past records to recognize in a story, knowing it took place, not that it still holds.