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/bl1nk-bot/bl1nk-agents-managerWrote 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/bl1nk-bot/bl1nk-agents-manager/thoughts-locator)<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/thoughts-locator"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/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/bl1nk-bot/bl1nk-agents-manager/thoughts-locator"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/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.00025 | $0.00864 |
| Opus 5 | $0.00013 | $0.00432 |
| Sonnet 5 | $0.00005 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 124 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/architecture/ for important architectural design and decisions
- Check thoughts/research/ for previous research
- Check thoughts/plans/ for previous ipmlentation plans
- Check thoughts/tickets/ for current tickets that are unstarted or in progress
-
Categorize findings by type
- Architecture in architecture/
- Tickets in tickets/
- Research in research/
- Implementation in plans/
- Reviews in reviews/
-
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/architecture/ # Architecture design and decisions thoughts/tickets/ # Ticket documentation thoughts/research/ # Research documents thoughts/plans/ # Implementation plans thoughts/reviews/ # Code Reviews
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]
### Architecture
- `thoughts/architecture/core-design.md - Namespace design`
### Tickets
- `thoughts/tickets/eng_1234.md` - Implement rate limiting for API
### Research
- `thoughtsresearch/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/plans/api-rate-limiting.md` - Detailed implementation plan for rate limits
### Related Discussions
- `thoughts/user/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
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.
- 12d ago First seen · 124 lines · 25 tokens per session scan A 355e10f86284
thoughts-locator is an agent published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 864 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
content-writer
Platform-specific content generator conditioned on your persona, voice, and trend topics.
trendsetter
Domain trend detector that recommends content topics based on your persona.
admin
Publisher and performance tracker that manages content lifecycle and feedback loop.
virtual-follower
QA simulator that evaluates content drafts as virtual followers and recommends TOP 5.
profiler
Deep psychology-based interviewer that extracts unconscious patterns across 10 frameworks.
integration-architect
The Master Orchestrator for Integration Architecture. Use this agent when you need to: Design end-to-end API contracts from legacy docs to mobile frontends Run the full 5-phase integration lifecycle (Discovery → UI Analysis → Contract Design → DB Alignment → Quality) Coordinate multiple specialized agents for a…