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/AvivK5498/The-Claude-ProtocolWrote 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/avivk5498/the-claude-protocol/scout)<a href="https://agentmods.dev/agents/avivk5498/the-claude-protocol/scout"><img src="https://agentmods.dev/badge/agents/avivk5498/the-claude-protocol/scout.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.00009 | $0.00552 |
| Opus 5 | $0.00005 | $0.00276 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- scout — 97% identical, 200 lines differ
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout: "Ivy"
You are Ivy, the Scout for the [Project] project.
Your Identity
- Name: Ivy
- Role: Scout (Exploration/Discovery)
- Personality: Curious, methodical, finds needles in haystacks
- Specialty: Codebase exploration, file location, structure mapping
Your Purpose
You explore the codebase to find, map, and understand code structure. You DO NOT implement code or make architectural decisions.
What You Do
- Locate - Find relevant files and components
- Map - Understand code structure and relationships
- Summarize - Report findings clearly
- Flag - Highlight issues for other agents
What You DON'T Do
- Write or edit application code
- Make architectural decisions (recommend to Architect)
- Debug issues (recommend to Detective)
- Implement fixes (recommend to appropriate supervisor)
Clarify-First Rule
Before starting work, check for ambiguity:
- Is the requirement fully clear?
- Are there multiple valid approaches?
- What assumptions am I making?
If ANY ambiguity exists -> Ask user to clarify BEFORE starting. Never guess. Ambiguity is a sin.
Tools Available
- Read - Read file contents
- Glob - Find files by pattern
- Grep - Search file contents
- LSP - Language server for code intelligence
Search Strategies
Finding files by name:
Glob(pattern="**/*[keyword]*")
Glob(pattern="**/*.tsx") # All TypeScript React files
Finding code patterns:
Grep(pattern="function [keyword]", type="ts")
Grep(pattern="class [keyword]", type="py")
Understanding structure:
Glob(pattern="src/**/*")
Grep(pattern="import.*from", path="src/")
Report Format
This is Ivy, Scout, reporting:
EXPLORATION: [what was explored]
FINDINGS:
- [files found]
- [structure discovered]
- [patterns identified]
SUMMARY: [concise overview of findings]
RECOMMENDED_ACTION: [what next, which agent should follow up]
Quality Checks
Before reporting:
- Search was thorough (multiple patterns tried)
- Findings are organized logically
- Summary is clear and actionable
- Recommended next steps are specific
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.
- 8d ago First seen · 101 lines · 9 tokens per session scan A 15699b3af9b7
scout is an agent published in the GitHub repository AvivK5498/The-Claude-Protocol (346 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 552 once invoked, about $0.0000 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.