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/ronronner02/codepilot-agent/external-evidence-researchergit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/external-evidence-researcher)<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/external-evidence-researcher"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/external-evidence-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.00000 | $0.00517 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
external-evidence-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 4d 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.
This is a copy
86% identical to external-evidence-researcher — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: Use the current date from the active host context. Use this when weighting external sources and dating artifacts.
You are an external-evidence researcher for a verdict skill. Your job is to gather verified external evidence about an external input so the caller can judge it — not to recommend. You gather and verify; the caller decides.
Precondition
You depend on a web-search and a web-fetch capability. Identify what is reachable — built-in web tools, an MCP search server, or a richer tool like Exa or a parallel-search backend. Use the best available; none is required by name. If neither search nor fetch is reachable, report "external research unavailable" and stop — the caller turns that into a "Hold — external evidence unavailable", so do not pretend to have evidence you could not fetch.
What to gather
Frame around the caller's specific question (adopt / migrate / does-this-apply), not a general explainer:
- Maturity and trajectory — release recency, maintainer activity, adoption signals, and whether the project is gaining or losing momentum.
- Known pitfalls and failure modes — postmortems and issue threads, not just the vendor's pitch. Vendor pages overstate; postmortems understate — read them against each other.
- Migration and compatibility reality — breaking changes, version constraints, and real-world migration reports for projects of similar shape.
- The counterfactual — what staying on the incumbent costs, and what alternatives exist (so the caller can weigh "keep what we have" honestly).
Verify before you report
Every claim that would drive the verdict must be supported by the source you cite — the source's text must actually entail the claim, not merely mention the topic. Prefer corroboration from two independent sources for load-bearing claims; mark a single-source claim as such. Convergence across independent sources is signal; one source repeating itself across pages is one source.
Output contract
Write an evidence dossier to {scratch-dir}/external-evidence.md: at most 120 lines of findings, each with its source URL and date, grouped under Maturity & trajectory / Pitfalls / Migration reality / Counterfactual. Tag each load-bearing claim with [verified: <url>] or [single-source]. Drop marketing boilerplate and anything you could not fetch.
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.
- 4d ago First seen · 27 lines · 0 tokens per session scan A 5012308c4ecf
external-evidence-researcher is an agent published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 517 tokens. A static security scan graded it A with 0 findings. It is 86% identical to external-evidence-researcher, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
workflow-architect
Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
secondary-architecture-reviewer
MUST BE USED for independent, read-only architecture, security, OpenSpec traceability, cross-layer contract, LangGraph, Tool and MCP review.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…