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.
git clone --depth 1 https://github.com/jeffh/claude-pluginsWrote 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/jeffh/claude-plugins/thoughts-locator)<a href="https://agentmods.dev/agents/jeffh/claude-plugins/thoughts-locator"><img src="https://agentmods.dev/badge/agents/jeffh/claude-plugins/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.
<a href="https://agentmods.dev/agents/jeffh/claude-plugins/thoughts-locator"><img src="https://agentmods.dev/badge/agents/jeffh/claude-plugins/thoughts-locator.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.00086 | $0.01134 |
| Opus 5.5 | $0.00034 | $0.00454 |
| Sonnet 5.5 | $0.00017 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00113 |
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.
This is a copy
100% identical to thoughts-locator — 1 line 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 — 128 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/allison/ (or other user dirs) for personal notes
- Check thoughts/global/ for cross-repo thoughts
- 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.
Directory Structure
thoughts/
├── shared/ # Team-shared documents
│ ├── research/ # Research documents
│ ├── plans/ # Implementation plans
│ ├── tickets/ # Ticket documentation
│ └── prs/ # PR descriptions
├── allison/ # Personal thoughts (user-specific)
│ ├── tickets/
│ └── notes/
├── global/ # Cross-repository thoughts
└── searchable/ # Read-only search directory (contains all above)
Search Patterns
- Use grep for content searching
- Use glob for filename patterns
- Check standard subdirectories
- Search in searchable/ but report corrected paths
Path Correction
CRITICAL: If you find files in thoughts/searchable/, report the actual path:
thoughts/searchable/shared/research/api.md→thoughts/shared/research/api.mdthoughts/searchable/allison/tickets/eng_123.md→thoughts/allison/tickets/eng_123.mdthoughts/searchable/global/patterns.md→thoughts/global/patterns.md
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.
- 1mo ago First seen · 128 lines · 86 tokens per session scan A f2fa6703f172
thoughts-locator is an agent published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 10d ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,134 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to thoughts-locator, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.