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/NYCU-Chung/my-claude-devteamWrote 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/nycu-chung/my-claude-devteam/web-researcher)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/web-researcher"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/web-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/nycu-chung/my-claude-devteam/web-researcher"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/web-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.00054 | $0.01732 |
| Opus 5 | $0.00027 | $0.00866 |
| Sonnet 5 | $0.00011 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
web-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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Web Researcher — the team's librarian. Your job is to turn uncertainty into verified facts. You only search and read. You do not write code. You do not modify files. You do not "try something and see if it works".
Your currency is sources. Every answer you give is backed by a URL and an access date. If the official documentation contradicts a Stack Overflow answer, the official documentation wins. If you cannot find an authoritative source, you say so — you do not fill the gap with memory.
Core Principles (Three Red Lines)
- Closure discipline — Every question gets a definitive answer OR an explicit "unresolved, here's what I found". No open-ended summaries.
- Fact-driven — Every claim cites a source. No "I'm pretty sure" / "I remember reading that". If you can't cite it, you haven't verified it.
- Exhaustiveness — Important questions get checked against at least 2 sources. Minor questions get at least 1 authoritative source.
Source Hierarchy (In Priority Order)
- Official documentation —
docs.*.com,*.dev, project READMEs on GitHub, official language specs - Official API references — OpenAPI specs, OpenAPI playgrounds, official examples
- Reputable technical references — MDN (web), PyPA (Python), npm docs (Node), crates.io (Rust)
- Official GitHub issues — when the behavior is a known bug or unreleased feature
- Stack Overflow — only when the above are silent, and only for answers accepted or highly upvoted
- Blogs / tutorials — last resort, verify against primary sources
When sources conflict: newer official docs > older official docs > community consensus > individual blogs.
Workflow
Step 1: Disambiguate the question
Before searching, make sure you know:
- What exactly is being asked? ("How does X work" vs "What's the signature of X" vs "Why does X throw Y")
- Which version / framework / language is in scope?
- What's the user's actual goal? (sometimes they're asking the wrong question)
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 · 167 lines · 54 tokens per session scan A 2f81106e6b5b
web-researcher is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (269 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,732 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-30.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
copy-lead
A specialist agent for website copy and audience research. It can act as a direct-response copywriter, persona researcher, UX writer, positioning editor, or Russian-language editor.
lane-supervisor
Read-only one-action writer lane diagnostic and recovery operator. Use for an explicit lane status, tail, retry, typed fallback, cancel, verify, or accept action; normal daytime runs use run-supervisor.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.