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 find-duplicatesgit 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/find-duplicates)<a href="https://agentmods.dev/skills/obsfx/trekker-claude-code/find-duplicates"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/find-duplicates/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/find-duplicates"><img src="https://agentmods.dev/badge/skills/obsfx/trekker-claude-code/find-duplicates.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.00021 | $0.00399 |
| Opus 5.5 | $0.00008 | $0.00160 |
| Sonnet 5.5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
find-duplicates 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 find-duplicates — 6 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.
What it actually says
CRITICAL: Search Before Creating ANY Task
You MUST search before creating any task.
trekker search "<task description you're about to create>"
When to Use (MANDATORY)
- BEFORE creating ANY new task - non-negotiable
- User reports issue - check if already tracked
- Grooming backlog - find consolidation opportunities
- Starting new feature - find related past work
IMPORTANT: FTS5 Search Tips
Search uses FTS5 (not semantic). Use single keywords for best recall:
- Multi-word queries require ALL words present (AND logic = fewer results)
- Search multiple times with different keywords
Commands
# Search with single keywords - try the most distinctive word
trekker search "authentication"
trekker search "login"
# Search specific type
trekker search "timeout" --type task
# Search by status
trekker search "performance" --status todo
MANDATORY Workflow
1. SEARCH: trekker search "<single keyword>" (try 2-3 keywords separately)
2. REVIEW results
3. DECIDE:
- Found exact match → DO NOT create, update existing task
- Found related work → Review carefully, may need to link
- No results → Safe to create new
4. CREATE in Trekker FIRST (if no duplicate)
5. MIRROR to TodoWrite after
Anti-Patterns (DO NOT)
- Creating task without searching first
- Ignoring search results
- Creating in TodoWrite without checking Trekker first
Trekker is Primary
Always:
- Check Trekker for duplicates FIRST
- Create in Trekker FIRST
- Then mirror to TodoWrite
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 First seen · 66 lines · 21 tokens per session scan A 8ce762abc700
find-duplicates is a skill published in the GitHub repository obsfx/trekker-claude-code (4 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 399 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 find-duplicates, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next
Manage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
execute-round
Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.