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 skills add ccashwell/evm-cortex --skill audit-recongit clone --depth 1 https://github.com/ccashwell/evm-cortexWrote 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/skills/ccashwell/evm-cortex/audit-recon)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/audit-recon"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/audit-recon/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/skills/ccashwell/evm-cortex/audit-recon"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/audit-recon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01461 |
| Opus 5.5 | $0.00015 | $0.00584 |
| Sonnet 5.5 | $0.00008 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
audit-recon 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Reconnaissance
Phase Overview
Recon is the first phase of a security audit. The goal is to build a mental model of the system before diving into code. Spend 10-20% of total audit time here.
Step 1: Automated Tools First
Run automated scanners to identify low-hanging fruit and build familiarity:
# Slither — static analysis
slither . --filter-paths "test|script|node_modules" \
--print human-summary \
--print contract-summary
# Aderyn — Solidity-specific linter
aderyn . --exclude test/ --output aderyn-report.md
# Solidity Metrics — complexity and SLOC
solidity-metrics src/
# Dependency tree
forge tree
Slither Detectors to Focus On
| Detector | Severity | What It Finds |
|---|---|---|
reentrancy-eth |
High | ETH reentrancy |
reentrancy-no-eth |
Medium | State reentrancy |
unchecked-transfer |
High | Unchecked ERC20 returns |
arbitrary-send-eth |
High | Uncontrolled ETH transfer |
suicidal |
High | Unprotected selfdestruct |
uninitialized-state |
High | Uninitialized variables |
controlled-delegatecall |
High | User-controlled delegatecall |
Slither Printers for Recon
# Call graph
slither . --print call-graph
# Function summary (visibility, modifiers, state changes)
slither . --print function-summary
# Inheritance graph
slither . --print inheritance-graph
# Variables read/written per function
slither . --print vars-and-auth
Step 2: Dependency Review
# List all dependencies and versions
forge tree
# Check for known vulnerabilities
# Cross-reference OpenZeppelin version against security advisories
# https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories
Key questions:
- Are dependencies pinned to specific commits/versions?
- Any modified/forked dependencies?
- Solidity compiler version — known compiler bugs?
Step 3: Architecture Mapping
Build this map by reading code, starting from entry points:
## Contract Map
### Core
- Vault.sol (512 SLOC) — main entry point
- Inherits: ERC4626, Ownable, ReentrancyGuard, Pausable
- External calls: Strategy, Oracle, USDC
- State: deposits, withdrawals, share pricing
### Periphery
- Strategy.sol (189 SLOC) — yield deployment
- External calls: Aave Pool, USDC
- Called by: Vault (only)
### Libraries
- MathLib.sol (45 SLOC) — fixed-point math
- Pure functions, no state
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 · 214 lines · 38 tokens per session scan A 800dfceca0b3
audit-recon is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 38 tokens to every session and 1,461 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…