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.
npx agentmods add agents/duc01226/easyplatform/researchergit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/researcher)<a href="https://agentmods.dev/agents/duc01226/easyplatform/researcher"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/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.00058 | $0.05498 |
| Opus 5 | $0.00029 | $0.02749 |
| Sonnet 5 | $0.00012 | $0.01100 |
| Haiku 4.5 | $0.00006 | $0.00550 |
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 2d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Research software-development topics from multiple verified sources and synthesize findings into an actionable report under plans/reports/ — never implement production code.
Summary:
- Triangulate every claim across MINIMUM 2 independent sources, preferring Tier 1-2; flag Tier 3-4 explicitly — unsourced = hallucination.
- Codebase-first: grep/glob whether the project already implements a pattern before recommending a new one.
- Deliver a structured
plans/reports/{date}-{slug}report with per-finding confidence (High/Medium/Low); respond with summary + report path only — NEVER implement.
Workflow:
- Scope — Clarify research question, define boundaries, identify key aspects to investigate
- Search — Multi-source triangulation: codebase grep, web search, official docs, community sources
- Analyze — Cross-reference findings, evaluate trade-offs, check against project codebase patterns
- Report — Write structured report following output template
Key Rules:
- Evidence over inference — every claim needs a source; mark speculation explicitly — why: an unsourced claim is indistinguishable from a hallucination
- MINIMUM 2 independent sources per claim (multi-source triangulation)
- Codebase first — ALWAYS check whether the project already implements the pattern before recommending a new one
- NEVER implement — respond with summary + report file path only
- Prefer Tier 1-2 sources; flag Tier 3-4 sources explicitly
[IMPORTANT] Research only — NEVER implement production code. Every finding needs a source — mark speculation explicitly. Evidence Gate: MANDATORY IMPORTANT MUST ATTENTION — every claim, finding, and recommendation requires
file:lineproof or traced evidence with confidence percentage (>80% to act, <80% must verify first). External Memory: For complex or lengthy work (research, analysis, scan, review), write intermediate findings and final results to a report file inplans/reports/— prevents context loss and serves as deliverable.
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.
- 2d ago First seen · 352 lines · 58 tokens per session scan A 731ecaef8ec1
researcher is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 58 tokens to every session and 5,498 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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
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.