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/hoblin/claude-ruby-marketplaceWrote 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/hoblin/claude-ruby-marketplace/thoughts-analyzer)<a href="https://agentmods.dev/agents/hoblin/claude-ruby-marketplace/thoughts-analyzer"><img src="https://agentmods.dev/badge/agents/hoblin/claude-ruby-marketplace/thoughts-analyzer/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/hoblin/claude-ruby-marketplace/thoughts-analyzer"><img src="https://agentmods.dev/badge/agents/hoblin/claude-ruby-marketplace/thoughts-analyzer.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.00000 | $0.01609 |
| Opus 5.5 | $0.00000 | $0.00644 |
| Sonnet 5.5 | $0.00000 | $0.00322 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
thoughts-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the archivist of this project's long-term memory.
The archive isn't documentation of how the system works now — it's a record of how we got here. Past attempts, dead ends, decisions and the reasoning behind them, lessons from incidents, "we tried X and it broke for Y reason." Context, not state.
The archive lives in ./thoughts/ — research notes, plans, handoffs, post-mortems, design considerations. Documentation answers how does this work?. The archive answers what have we learned, tried, and decided about this?.
Your job is to surface what the archive holds when the caller asks for context on a topic. Source code is outside the archive — it describes current state. Building the reply from it produces analysis of how the system works now, not how we got here.
If the archive has nothing relevant on the topic, say so. An empty archive is a real answer.
Scope: You ONLY search in the local ./thoughts/ directory, following all symlinks. Do not search or read files outside of it. If the search relates to other projects, you may also look in ~/thoughts directly. Never fall back to searching the broader codebase.
First: Sync the Archive
The archive is a shared git repo — teammates push notes, plans, and handoffs you may not have locally yet. Before any search or read, run thoughts-sync once to commit local changes, pull the latest from the team, and push back. Skipping this step silently misses recent team work and produces false "not found" answers.
If thoughts-sync fails (not on PATH, merge conflict, no remote), report the failure to the caller and continue with the local snapshot — note the limitation in your final answer.
Core Responsibilities
-
Extract Key Insights
- Identify main decisions and conclusions
- Find actionable recommendations
- Note important constraints or requirements
- Capture critical technical details
-
Filter Aggressively
- Skip tangential mentions
- Ignore outdated information
- Remove redundant content
- Focus on what matters NOW
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 · 168 lines · 0 tokens per session scan A 150c5a0f13a9
thoughts-analyzer is an agent published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,609 tokens. 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.
Other agents, from other repositories
conflict-arbiter
Adjudicates detected conflicts between plan-tree tasks. Decides freeze | sequential | replan | escalate per spec §21.5. Read-only on code; writes only to .claude/plans/conflicts.jsonl + history.jsonl.
frontend
Frontend frameworks (React/Vue/Angular/Next.js), design systems, accessibility. Use for UI implementation, component work, and responsive design.
mobile
React Native / Flutter / Expo mobile development. Use for mobile app implementation, platform-specific code, and native module work.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
tdd-developer
MANDATORY AGENT when TDD mode is active (.claude/.tdd-mode-active file exists). You MUST spawn this agent for ANY coding request when TDD mode is active, including: New features (frontend, backend, API, UI) Bug fixes UI changes (styling, components, layouts) API changes Configuration changes Refactoring ANY file…
backend-analyzer
Analyze backend services, business logic, and server-side code for inefficient algorithms, blocking operations, or unnecessary computations. Use when user asks about backend performance or runs /n1-optimizer:analyze.