thoughts-locator

thoughts-locator is an agent for Claude Code from eveld/claude. It costs 86 tokens per session (1,447 once invoked), scanned A, a copy of thoughts-locator, MIT.

A document finder for the thoughts/ directory, which stores personal notes, team documents, research, plans, tickets, and meeting records. It locates matching files and groups them by type.

In plain words
What is it for?
Use it to search personal, shared, and project-wide notes, then get organized results with brief descriptions, dates, and corrected file paths.
Why use it?
It helps when useful project knowledge may be buried in many folders and filenames. It finds likely documents without trying to analyze their contents deeply.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the workflows plugin — 29 skills, 5 commands, 17 agents shipped together

Good fit Use it to search personal, shared, and project-wide notes, then get organized results with brief descriptions, dates, and corrected file paths.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eveld/claude/thoughts-locator
View source ↗ eveld/claude
Install

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.

Clone the repo
git clone --depth 1 https://github.com/eveld/claude

Made for: Claude Code.

Or install workflows, the plugin that ships this one along with the rest of its 29 skills, 5 commands, 17 agents.

Wrote 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.

agentmods badge for thoughts-locator

README.md
[![agentmods](https://agentmods.dev/badge/agents/eveld/claude/thoughts-locator/github.svg)](https://agentmods.dev/agents/eveld/claude/thoughts-locator)
Your own site
<a href="https://agentmods.dev/agents/eveld/claude/thoughts-locator"><img src="https://agentmods.dev/badge/agents/eveld/claude/thoughts-locator/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.

agentmods 80×15 button for thoughts-locator

Your own site · 80×15
<a href="https://agentmods.dev/agents/eveld/claude/thoughts-locator"><img src="https://agentmods.dev/badge/agents/eveld/claude/thoughts-locator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,447 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.01447
Opus 5.5 $0.00034 $0.00579
Sonnet 5.5 $0.00017 $0.00289
Haiku 4.5 $0.00009 $0.00145

Measured 1mo ago against content hash 1cb350537aa1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

92% identical to thoughts-locator — 80 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.

agents/thoughts-locator.md · 149 lines

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

  1. 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)
  2. 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
  3. 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:

  1. Shared feature directories: thoughts/shared/NNNN-*/ (published team docs)
  2. Personal feature directories: thoughts/{username}/NNNN-*/ (work-in-progress)
  3. Project-wide notes: thoughts/notes/
  4. Legacy shared directories: thoughts/shared/research/, thoughts/shared/plans/
  5. 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)

Read the full file on GitHub · 149 lines

Changes

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.

  1. 1mo ago First seen · 149 lines · 86 tokens per session scan A 1cb350537aa1

Subscribe to this mod's changes

thoughts-locator is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 8mo ago), licensed MIT. It adds 86 tokens to every session and 1,447 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to thoughts-locator, differing in 80 lines, and is treated as a copy.

Related

Other agents, from other repositories

deep-research-patcher

Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.

qf-studio/navigator · 55 tokens

product-analytics-specialist

PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…

travisjneuman/.claude · 80 tokens

migration-specialist

Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…

travisjneuman/.claude · 67 tokens

monetization-expert

Expert in revenue models, pricing strategy, and business monetization.

travisjneuman/.claude · 18 tokens

CodeQL Permissions Auditor

Analyze workflow permission issues and apply fixes.

dryvist/claude-code-plugins · 12 tokens

state-keeper

Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…

fakoli/fakoli-plugins · 465 tokens