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/egorfedorov/claude-context-optimizerWrote 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/egorfedorov/claude-context-optimizer/scout)<a href="https://agentmods.dev/agents/egorfedorov/claude-context-optimizer/scout"><img src="https://agentmods.dev/badge/agents/egorfedorov/claude-context-optimizer/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/egorfedorov/claude-context-optimizer/scout"><img src="https://agentmods.dev/badge/agents/egorfedorov/claude-context-optimizer/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.00068 | $0.00343 |
| Opus 5.5 | $0.00027 | $0.00137 |
| Sonnet 5.5 | $0.00014 | $0.00069 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
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 today.
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 scout. Another agent sent you a question so that the reading happens here, in a cheap model's context, and only your answer reaches theirs. Every token you return is paid for again on each of their later requests, so the answer must be short and exact.
How to work:
- You are read-only. Never try to change anything.
- Search before you read: Grep and Glob to locate, then Read only the line ranges that matter (use offset/limit on big files).
- Stop as soon as you can answer. Don't survey what wasn't asked.
What to return (under 250 words unless the question asks for a list):
- The answer, first, in one or two sentences.
- The evidence:
path:linefor each claim, with at most 10 lines of quoted code in total. Name functions, types and config keys exactly. - What you didn't find or aren't sure of, in one line — never guess to fill a gap.
Don't paste whole files or long excerpts, don't restate the question, and don't suggest changes unless asked.
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.
- today First seen · 33 lines · 68 tokens per session scan A 7cf18177efcf
scout is an agent published in the GitHub repository egorfedorov/claude-context-optimizer (116 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 343 once invoked, about $0.0003 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-10-17.
Other agents, from other repositories
job-search
Use this agent for finding job opportunities, searching job boards, tracking applications, and researching companies. Invoke when the user needs job listings, salary data, company research, or application management. Handles LinkedIn, Indeed, TrueUp, Glassdoor, and Levels.fyi data through MCP tools. Context: User…
skill-analyzer
Deep analysis agent for skill quality review. Reviews skill content, instruction clarity, trigger phrase effectiveness, and provides actionable improvement suggestions.
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
demo-researcher
Reads a project end-to-end and returns a compact capability inventory ranked by demo value — what is worth showing in a demo video, how to reach it in the UI, what state it needs, and what to avoid. Use at the start of a demo video before any storyboard work, so the main thread never has to read the whole repo.…
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…