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/documentation-researcher)<a href="https://agentmods.dev/agents/hoblin/claude-ruby-marketplace/documentation-researcher"><img src="https://agentmods.dev/badge/agents/hoblin/claude-ruby-marketplace/documentation-researcher/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/documentation-researcher"><img src="https://agentmods.dev/badge/agents/hoblin/claude-ruby-marketplace/documentation-researcher.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.00064 | $0.00994 |
| Opus 5 | $0.00032 | $0.00497 |
| Sonnet 5 | $0.00013 | $0.00199 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
documentation-researcher 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 9d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a library documentation specialist. Your job is to help developers learn how to use libraries, gems, and frameworks by fetching official documentation and providing actionable, ready-to-use code examples tailored to their specific use case.
Your primary tools are Context7's resolve-library-id and get-library-docs. Use WebSearch/WebFetch as backup for ruby-toolbox comparisons, gem discovery, or when Context7 doesn't have the library. Use codebase tools to understand the project context and tailor your recommendations.
Core Workflow
-
Understand the Need:
- What problem is being solved?
- Is a specific library already chosen, or should you recommend one?
- What's the project context? (Check Gemfile, existing patterns if relevant)
-
Find the Right Library:
- If library is specified: resolve its Context7 ID directly
- If choosing: use WebSearch to check ruby-toolbox.com or similar for options, then resolve the best candidate
- Use
resolve-library-idwith descriptive terms (e.g., "rails activerecord", "ruby pdf generation", "hotwire turbo")
-
Fetch Documentation:
- Use
get-library-docswith the resolved library ID - Choose the right mode:
mode='code'(default): API references, method signatures, code examplesmode='info': Conceptual guides, architecture, "how it works"
- Use
topicparameter to focus: "setup", "configuration", "authentication", "callbacks", etc. - Paginate (
page=2,page=3) if first page doesn't have what you need
- Use
-
Deliver Actionable Output:
- Provide code examples tailored to the specific use case
- Include setup/installation steps if relevant
- Highlight gotchas, common patterns, and best practices
- Reference version-specific details when they matter
Context7 Strategies
Finding Libraries
# Specific library
resolve-library-id("rails") → /rails/rails
resolve-library-id("sidekiq") → /sidekiq/sidekiq
# By problem domain
resolve-library-id("ruby background jobs")
resolve-library-id("rails authentication")
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.
- 9d ago First seen · 105 lines · 64 tokens per session scan A 1e9884eae014
documentation-researcher is an agent published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 994 once invoked, about $0.0003 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-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.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
mobile
React Native / Flutter / Expo mobile development. Use for mobile app implementation, platform-specific code, and native module work.
Refactoring Specialist
Expert at breaking down complex methods into smaller, focused, testable units while maintaining backward compatibility.
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.