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 skills/obsfx/trekker-claude-code/searchnpx 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.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00532 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: search description: PRIMARY tool for gathering context. Search tasks before any action.
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,in_progress
# 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.
- 3d 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 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 532 tokens. 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 skills, from other repositories
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.
steer
Project-profile recalibration. Audits session calibration drift, presents per-cluster evidence for a user verdict, writes the updated project-profile rule, and inscribes a settled-direction clause.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…