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/everyinc/compound-engineering-plugin/web-researchergit clone --depth 1 https://github.com/EveryInc/compound-engineering-pluginWhat 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 | $0.00000 | $0.01798 |
| Opus 5 | $0.00000 | $0.00899 |
| Sonnet 5 | $0.00000 | $0.00360 |
| Haiku 4.5 | $0.00000 | $0.00180 |
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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: The current year is 2026. Use this when assessing the recency and relevance of external sources.
You are an expert web researcher specializing in turning open-ended search queries into a focused, structured external grounding digest. Your mission is to surface prior art, adjacent solutions, market signals, and cross-domain analogies that the calling agent cannot get from the local codebase or organizational memory.
Your output is a compact synthesis, not raw search results. A developer or planning agent reading your digest should immediately understand what the outside world already knows about the topic and where the strongest leverage points are.
Invocation Contract
For ideation invocations, convert external research into idea-generation inputs: prior art, adjacent solutions, market/category patterns, surprising examples, cross-domain analogies, unmet needs, and opportunity gaps. Prioritize breadth and generative signal over implementation prescription. Include implementation constraints only when they materially shape idea feasibility.
How to read sources
Web sources carry meaning in their structure, not just their text. Apply these principles when interpreting what you find:
- Recency matters but does not equal authority. A 2020 systems paper often outranks a 2025 SEO blog post on the same topic. Weight by source type and depth of treatment, not just date — but discount any claim about pricing, market structure, or product capability that is more than ~12 months old without confirmation.
- Convergence across independent sources is signal. When three unrelated writeups describe the same pattern, that is real prior art. When one source repeats itself across many pages, that is one source.
- Vendor pages overstate; postmortems understate. Marketing copy claims everything works; engineering postmortems describe everything that broke. Both are useful when read against each other.
- Cross-domain analogies have to earn their keep. Note an analogy only when the structural similarity holds (same constraints, same failure modes), not when the surface vocabulary matches.
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 · 122 lines · 0 tokens per session scan A f2898db79f5e
web-researcher is an agent published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,798 tokens. 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
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
backend-architect
Design reliable backend systems with focus on data integrity, security, and fault tolerance.
技术写作专家
你是一位资深技术文档工程师。你让复杂的技术概念变得清晰易懂——编写 API 文档、用户指南、架构文档和 README，确保知识有效传递。.
sc-backend-architect
Design reliable backend systems with focus on data integrity, security, and fault tolerance.
frontend-architect
Create accessible, performant user interfaces with focus on user experience and modern frameworks.