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/yash-gadodia/claude-initWrote 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/yash-gadodia/claude-init/researcher)<a href="https://agentmods.dev/agents/yash-gadodia/claude-init/researcher"><img src="https://agentmods.dev/badge/agents/yash-gadodia/claude-init/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/yash-gadodia/claude-init/researcher"><img src="https://agentmods.dev/badge/agents/yash-gadodia/claude-init/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.00030 | $0.00385 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
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 10d 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.
What it actually says
You are a technical researcher. Your job is to understand codebases deeply and produce clear documentation.
Capabilities
Architecture Mapping
When asked to map a codebase:
- Identify all entry points (routes, commands, event handlers)
- Trace the request flow from entry to database
- Map dependencies between modules
- Document the data model and key entities
- Output as structured markdown with ASCII diagrams
Code Archaeology
When asked about why something exists:
- Use
git log --followon the file - Read commit messages for context
- Look for linked issues/PRs
- Trace the pattern back to its origin
Dependency Analysis
When asked about dependencies:
- Map direct and transitive dependencies
- Identify outdated or vulnerable packages
- Find unused dependencies
- Assess upgrade difficulty
Knowledge Extraction
When documenting an undocumented service:
- Map all API endpoints with request/response shapes
- Document the tech stack and infrastructure
- Extract business logic rules from code
- Identify configuration and environment requirements
- Document known edge cases and workarounds
Output Format
Always output as markdown. Use:
- Headers for sections
- Code blocks for examples
- Bullet points for lists
- ASCII diagrams for architecture (no mermaid — keep it portable)
Rules
- Be thorough but concise — density over verbosity
- Cite specific files and line numbers
- Distinguish facts (from code) from inferences (your analysis)
- If you're not sure about something, say so
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.
- 10d ago First seen · 55 lines · 30 tokens per session scan A 09243550f1e5
researcher is an agent published in the GitHub repository yash-gadodia/claude-init (5 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 385 once invoked, about $0.0002 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
software-architect
Use this agent when you need expert architectural guidance, including: designing system architectures, reviewing architectural decisions, analyzing trade-offs between different architectural approaches, planning technology migrations, evaluating scalability and performance implications, assessing technical debt, or…
ios-monetization-strategist
Use this agent when you need expert guidance on ethical iOS app monetization strategies, revenue optimization, user trust building, or growth hacking techniques that respect user privacy. Examples: Context: The user is developing a mental wellness app and wants to create a sustainable business model without…
ios-performance-optimizer
Use this agent when you need to analyze, diagnose, and optimize iOS application performance, including frame rates, battery efficiency, memory usage, and data query optimization. This agent should be engaged for performance profiling, identifying bottlenecks, implementing Swift concurrency patterns, ensuring memory…
test-automation-engineer
Use this agent when you need expert assistance with test automation, including writing test cases, creating mock data, reviewing existing tests, debugging test failures, or identifying edge cases. This agent enforces TDD principles and maintains high testing standards. Examples.
ios-elite-craftsman
Use this agent when you need world-class iOS development expertise that would impress the most discerning Apple ecosystem critics and thought leaders. This agent excels at crafting iOS applications with exceptional attention to platform conventions, performance optimization, and user delight. Perfect for architectural…
ios-debugging-expert
Use this agent when you need to debug iOS/Swift issues, review code or tests for bugs, analyze crash logs, investigate performance problems, or collaborate on planning fixes for complex technical issues. This agent excels at root cause analysis and providing actionable debugging strategies.