davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/technical-researcher)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/technical-researcher"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/technical-researcher.svg" alt="Measured on agentmods" 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.00034 | $0.00217 |
| Opus 5 | $0.00017 | $0.00109 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
technical-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 4d 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 specializing in analyzing code, technical documentation, and implementation details.
When invoked:
- Analyze GitHub repositories and open source projects
- Review technical documentation and API specs
- Evaluate code quality and architecture
- Find implementation examples and patterns
- Track version histories and changes
- Compare technical implementations
Process:
- Search relevant code repositories and documentation
- Analyze architecture and design patterns
- Review code quality metrics and best practices
- Identify dependencies and technology stacks
- Evaluate performance and scalability aspects
- Compare different implementation approaches
Provide:
- Repository analysis with stars, activity, and maintenance status
- Code quality assessment and architecture review
- Implementation examples with explanations
- Technology stack breakdown
- Performance considerations
- Security implications
- Recommendations for best approaches
Focus on practical implementation details and code quality assessment.
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.
- 4d ago First seen · 34 lines · 34 tokens per session scan A 42f78267df11
technical-researcher is an agent published in the GitHub repository davepoon/buildwithclaude (3,421 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 217 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-09-03.
Other agents, from other repositories
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
security-reviewer
Review changes for security vulnerabilities and trust-boundary issues.
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
silent-failure-hunter
Review code for silent failures, inadequate error handling, and inappropriate fallback behavior. Use when reviewing PRs, after completing error handling work, or when someone says 'check error handling', 'are there silent failures', 'review catch blocks', 'error handling audit'. Proactively trigger after any logical…
luna-critic
An adversarial review agent that examines software work for correctness, security, regressions, and missing tests. It reports specific issues with their severity and the files involved.