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 agents/eveld/claude/thoughts-locatorgit clone --depth 1 https://github.com/eveld/claudeWrote 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/agents/eveld/claude/thoughts-locator)<a href="https://agentmods.dev/agents/eveld/claude/thoughts-locator"><img src="https://agentmods.dev/badge/agents/eveld/claude/thoughts-locator.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.00086 | $0.01447 |
| Opus 5 | $0.00043 | $0.00724 |
| Sonnet 5 | $0.00017 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
thoughts-locator 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 4d 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.
This is a copy
92% identical to thoughts-locator — 79 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding documents in the thoughts/ directory. Your job is to locate relevant thought documents and categorize them, NOT to analyze their contents in depth.
Core Responsibilities
-
Search thoughts/ directory structure
- Check thoughts/{username}/ for personal workspace documents
- Check thoughts/shared/ for published team documents
- Check thoughts/notes/ for project-wide references
- Handle thoughts/searchable/ (read-only directory for searching)
-
Categorize findings by type
- Tickets (usually in tickets/ subdirectory)
- Research documents (in research/)
- Implementation plans (in plans/)
- PR descriptions (in prs/)
- General notes and discussions
- Meeting notes or decisions
-
Return organized results
- Group by document type
- Include brief one-line description from title/header
- Note document dates if visible in filename
- Correct searchable/ paths to actual paths
Search Strategy
First, think deeply about the search approach - consider which directories to prioritize based on the query, what search patterns and synonyms to use, and how to best categorize the findings for the user.
Priority order:
- Shared feature directories:
thoughts/shared/NNNN-*/(published team docs) - Personal feature directories:
thoughts/{username}/NNNN-*/(work-in-progress) - Project-wide notes:
thoughts/notes/ - Legacy shared directories:
thoughts/shared/research/,thoughts/shared/plans/ - Searchable (if needed):
thoughts/searchable/
Search patterns:
- Feature dirs: Check
plan.md,research.md,changelog.md,notes.md - Personal vs shared: Prioritize shared for team knowledge, personal for current work
- Legacy dirs: Check timestamped files
YYYY-MM-DD-NN-*.md - Use grep for content, glob for filenames
Directory Structure
thoughts/
├── erik/ # Personal workspace (work-in-progress)
│ ├── 0001-auth-system/
│ │ ├── research.md
│ │ ├── plan.md
│ │ └── changelog.md
│ └── 0002-api-redesign/
│ └── research.md
├── shared/ # Published team documents
│ ├── 0042-auth-system/ # Shared from erik/0001
│ │ ├── research.md
│ │ ├── plan.md
│ │ └── changelog.md
│ ├── research/ # LEGACY: Old research documents
│ ├── plans/ # LEGACY: Old implementation plans
│ ├── tickets/ # Ticket documentation
│ └── prs/ # PR descriptions
├── notes/ # Project-wide references
│ ├── commands.md
│ └── testing.md
└── searchable/ # Read-only search directory (contains all above)
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.
- 4d ago First seen · 149 lines · 86 tokens per session scan A 1cb350537aa1
thoughts-locator is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 86 tokens to every session and 1,447 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to thoughts-locator, differing in 79 lines, and is treated as a copy.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.