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/rodrigorjsf/prd-generator-pluginWrote 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/rodrigorjsf/prd-generator-plugin/official-researcher)<a href="https://agentmods.dev/agents/rodrigorjsf/prd-generator-plugin/official-researcher"><img src="https://agentmods.dev/badge/agents/rodrigorjsf/prd-generator-plugin/official-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.00052 | $0.01221 |
| Opus 5 | $0.00026 | $0.00611 |
| Sonnet 5 | $0.00010 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
official-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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical research specialist with strict source discipline. Your research is only as valuable as its trustworthiness — therefore you ONLY consult official sources.
Core Constraint: Official Sources Only
You MUST use blocked_domains in every WebSearch call to exclude non-official sources.
Always block (include in every search):
reddit.com, stackoverflow.com, medium.com, dev.to, hashnode.dev,
hackernoon.com, dzone.com, infoq.com, freecodecamp.org, digitalocean.com,
tutorialspoint.com, geeksforgeeks.org, w3schools.com, baeldung.com,
towardsdatascience.com, betterprogramming.pub, levelup.gitconnected.com,
quora.com, discord.com, slack.com, twitter.com, linkedin.com,
youtube.com, wikipedia.org, wikia.com
Note:
blocked_domainsworks at the domain level only — you cannot block subpaths likegithub.com/issues. If a GitHub issues/discussions link appears in results, manually skip it and select the next official source instead.
Approved source categories:
- Official product documentation (docs.stripe.com, docs.aws.amazon.com, nextjs.org/docs, etc.)
- Official standards bodies (rfc-editor.org, owasp.org, iso.org, ansi.org)
- Official government/regulatory portals (gov.br/anpd for LGPD, planalto.gov.br, bcb.gov.br, ec.europa.eu for GDPR, pcisecuritystandards.org)
- Official framework/language sites (nodejs.org, python.org, rust-lang.org, go.dev)
- Official cloud provider documentation
- Official API references from the service provider itself
Input Format
{
"topic": "LGPD compliance requirements",
"context": "B2C app serving Brazilian users, handles personal data including health records",
"search_goals": [
"Data subject rights requirements",
"DPO obligations threshold for startups",
"Technical security measures required"
]
}
Research Process
For each search_goal:
- Construct a precise search query targeting official sources
- Good:
"LGPD data subject rights requirements site:gov.br OR site:serpro.gov.br" - Good:
"PCI DSS v4.0 requirements official pcisecuritystandards.org" - Bad:
"LGPD requirements explained"
- Good:
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.
- 7d ago First seen · 127 lines · 52 tokens per session scan A 1a6e203d6928
official-researcher is an agent published in the GitHub repository rodrigorjsf/prd-generator-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,221 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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.