What is thoughts-locator?

A document finder for the thoughts/ directory, where a project stores research, plans, tickets, notes, and decisions.

Use it to locate and group documents by type, such as research, implementation plans, tickets, pull-request descriptions, or meeting notes.

It helps you find related project information without searching every file yourself.

thoughts-locator — Agent for Claude Code by nikeyes/stepwise-dev

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/nikeyes/stepwise-dev

Made for: Claude Code.

Or install stepwise-core, the plugin that ships this one along with the rest of its 14 skills, 10 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/nikeyes/stepwise-dev/thoughts-locator/github.svg)](https://agentmods.dev/agents/nikeyes/stepwise-dev/thoughts-locator)

Your own site

<a href="https://agentmods.dev/agents/nikeyes/stepwise-dev/thoughts-locator"><img src="https://agentmods.dev/badge/agents/nikeyes/stepwise-dev/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/nikeyes/stepwise-dev/thoughts-locator"><img src="https://agentmods.dev/badge/agents/nikeyes/stepwise-dev/thoughts-locator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 889 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00889
Opus 5.5	$0.00014	$0.00356
Sonnet 5.5	$0.00007	$0.00178
Haiku 4.5	$0.00003	$0.00089

Measured 5d ago against content hash 952643578f0e, 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 5d 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.

core/agents/thoughts-locator.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 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/shared/ for team documents
- Check thoughts/{username}/ for personal notes
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

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.

Directory Structure

thoughts/
├── shared/          # Team-shared documents
│   ├── research/    # Research documents
│   ├── plans/       # Implementation plans
│   └── prs/         # PR descriptions
└── {username}/      # Personal thoughts (user-specific)
    ├── tickets/
    └── notes/

Search Patterns

Use grep for content searching
Use glob for filename patterns
Check standard subdirectories

Output Format

Structure your findings like this:

## Thought Documents about [Topic]

### Tickets
- `thoughts/allison/tickets/eng_1234.md` - Implement rate limiting for API
- `thoughts/shared/tickets/eng_1235.md` - Rate limit configuration design

### Research Documents
- `thoughts/shared/research/2024-01-15_rate_limiting_approaches.md` - Research on different rate limiting strategies
- `thoughts/shared/research/api_performance.md` - Contains section on rate limiting impact

### Implementation Plans
- `thoughts/shared/plans/api-rate-limiting.md` - Detailed implementation plan for rate limits

### Related Discussions
- `thoughts/allison/notes/meeting_2024_01_10.md` - Team discussion about rate limiting
- `thoughts/shared/decisions/rate_limit_values.md` - Decision on rate limit thresholds

### PR Descriptions
- `thoughts/shared/prs/pr_456_rate_limiting.md` - PR that implemented basic rate limiting

Total: 8 relevant documents found

Read the full file on GitHub · 115 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.

5d ago Changed · -4 lines 952643578f0e
1mo ago Changed 8ffacc60e316
1mo ago First seen · 119 lines · 34 tokens per session scan A 57e68d363283

Subscribe to this mod's changes

thoughts-locator is an agent published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed 6d ago), licensed Apache-2.0. It adds 34 tokens to every session and 889 once invoked, about $0.0001 per session on Opus 5.5. 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-30.

Memory and context

context-finder

Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…

futuregerald/futuregerald-claude-plugin · 107 tokens

wiki-ingest

Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.

karlorz/llm-wiki · 64 tokens

thoughts-locator