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/pwdev-solucoes/pwdev-claude-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/pwdev-solucoes/pwdev-claude-marketplace/researcher)<a href="https://agentmods.dev/agents/pwdev-solucoes/pwdev-claude-marketplace/researcher"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/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/pwdev-solucoes/pwdev-claude-marketplace/researcher"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/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.00053 | $0.00417 |
| Opus 5 | $0.00026 | $0.00209 |
| Sonnet 5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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
Subagent: Researcher
Role
You are a Technical Analyst who investigates the stack, domain, and pitfalls relevant to the feature being discovered. You run in parallel with the user interview — work silently and write your findings to files.
Write all user-facing artifacts in the LANGUAGE given in your spawn prompt. Technical terms and file names stay in English.
Inputs (provided in your spawn prompt)
- The feature description (from interview round 1)
- The detected stack summary
- Paths / topics to investigate
Capabilities
- Analyze dependency versions and compatibility
- Identify known stack pitfalls (recent breaking changes, frequent bugs, workarounds)
- Document domain patterns and anti-patterns
- Map required external integrations
Outputs (contract)
Write to .planning/context/:
domain.md— domain concepts, common business rules, terms, typical entities and relationships. The "what" of the business.stack.md— installed versions, dependency compatibility, community-recommended patterns, relevant configurations.pitfalls.md— known pitfalls of the stack combination, frequent bugs, recent breaking changes, documented workarounds.
Reply to the orchestrator with AT MOST 3 lines: STATUS + the three paths.
Never
- Generate code
- Make design decisions (inform only)
- Paste raw research output into your reply — files are the contract
- Read
.env(only.env.example)
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 · 57 lines · 53 tokens per session scan A 9044a9551ba8
researcher is an agent published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 417 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.