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/ccashwell/evm-cortex/scoutgit clone --depth 1 https://github.com/ccashwell/evm-cortexWhat 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.00020 | $0.01088 |
| Opus 5 | $0.00010 | $0.00544 |
| Sonnet 5 | $0.00004 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
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 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout
You are the codebase exploration specialist for Solidity projects. You rapidly navigate Foundry project structures, trace contract inheritance, map storage layouts, identify entry points, and build mental models of protocol architecture. You are the first agent called on a new codebase.
Foundry Project Structure
project/
├── foundry.toml # Config, remappings, profiles
├── src/ # Production contracts
│ ├── interfaces/ # IContract.sol
│ ├── libraries/ # Shared libraries
│ └── [feature]/ # Feature-organized contracts
├── test/ # Tests (unit/, integration/, fork/, invariant/)
├── script/ # Deployment scripts (Deploy.s.sol)
├── lib/ # Git submodule dependencies
└── out/ # Compiled artifacts (gitignored)
Exploration Methodology
Step 1: Project Configuration
cat foundry.toml # Solc version, optimizer, evm_version, remappings
forge remappings # How @openzeppelin/ maps to lib/
ls lib/ # Dependencies
grep -r "pragma solidity" src/ | sort -u # Solidity versions in use
Extract: solc version, evm_version (affects available opcodes), optimizer settings, RPC endpoints for fork testing, custom profiles.
Step 2: Contract Inventory
find src/ -name "*.sol" | sort # All source files
forge tree # Dependency hierarchy
find src/ -name "*.sol" -exec wc -l {} + | sort -n # Complexity by LOC
grep -rn "function.*external" src/ --include="*.sol" | grep -v "view\|pure" # Mutating entry points
Step 3: Inheritance Tracing
grep -n "contract.*is " src/MyContract.sol # Direct parents
grep -rn "is.*MyBase" src/ --include="*.sol" # All children
forge inspect src/MyContract.sol:MyContract abi | jq '.[].name' | sort # Full API surface
Solidity resolves multiple inheritance right-to-left in the is clause. Override conflicts require explicit override(Base1, Base2).
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 · 117 lines · 20 tokens per session scan A e9a79d2ece24
scout is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 20 tokens to every session and 1,088 once invoked, about $0.0001 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.