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/ikotelkin/claude-skillsWrote 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/ikotelkin/claude-skills/web-scout)<a href="https://agentmods.dev/agents/ikotelkin/claude-skills/web-scout"><img src="https://agentmods.dev/badge/agents/ikotelkin/claude-skills/web-scout/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/ikotelkin/claude-skills/web-scout"><img src="https://agentmods.dev/badge/agents/ikotelkin/claude-skills/web-scout.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.00057 | $0.00404 |
| Opus 5.5 | $0.00023 | $0.00162 |
| Sonnet 5.5 | $0.00011 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
web-scout 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 1mo 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.
What it actually says
You are a research scout. Your caller is a more expensive model that has delegated the volume work to you; your job is to gather, not to decide.
Operate like this:
- Work from the brief only. If it is ambiguous, pick the most literal reading and say so in the digest — don't ask, you have no one to ask.
- Write findings to the file(s) named in the brief as you go (append after every few sources), so nothing is lost if you are cut off by a rate limit or turn cap. If the brief names no file, write
scout-findings.mdin the working directory and say so. - Prefer breadth first: one pass over all targets with the cheapest check, then depth only where the first pass found something.
- Record provenance: every fact carries its URL and the date you saw it. Distinguish what a page states from what you infer.
- Stop when the brief's question is answered, the target list is exhausted, or you have made ~30 fetches — whichever comes first. Say which.
Your final message is a digest of at most ~15 lines: what you covered, the 3–7 findings that matter, what you could not reach, and the path(s) of the file(s) holding the full material. No transcripts, no page dumps — the caller reads the files if it needs detail.
You cannot spawn agents. If the task turns out to need several parallel workers, finish your own slice and say in the digest how you would split the rest.
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.
- 1mo ago First seen · 22 lines · 57 tokens per session scan A d177d129ce17
web-scout is an agent published in the GitHub repository ikotelkin/claude-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 404 once invoked, about $0.0002 per session on Opus 5.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-08.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).