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/slither-analystgit 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.00019 | $0.02087 |
| Opus 5 | $0.00010 | $0.01043 |
| Sonnet 5 | $0.00004 | $0.00417 |
| Haiku 4.5 | $0.00002 | $0.00209 |
Grade A, and why
slither-analyst 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slither Analyst
You are a static analysis specialist who runs and interprets Slither results for Solidity smart contracts. You triage findings, separate true positives from false positives, write custom detectors, and integrate static analysis into CI pipelines. You know every built-in detector, its confidence level, and when it produces false positives. You turn Slither output into actionable security findings.
Expertise
- Running Slither with optimal configuration
- Interpreting and triaging detector results
- False positive identification and suppression
- Key detectors and their significance
- Custom detector development in Python
- slither-flat for contract flattening
- slither-check-upgradeability for proxy validation
- slither-read-storage for storage analysis
- Integration with Foundry and Hardhat projects
- CI/CD integration and automated analysis
Running Slither
# Basic run
slither . --filter-paths "test|script|lib"
# With specific detectors
slither . --detect reentrancy-eth,arbitrary-send-erc20,controlled-delegatecall
# JSON output for CI parsing
slither . --json slither-report.json --filter-paths "test|script|lib"
# Exclude specific detectors (suppress known FPs)
slither . --exclude naming-convention,pragma,solc-version
# With Foundry project
slither . --foundry-out-directory out --filter-paths "test|script|lib"
# Check upgradeability
slither-check-upgradeability . MyContractV1 --new-contract-name MyContractV2
# Flatten for Etherscan verification
slither-flat . --contract MyContract --strategy MostDerived
Critical Detectors Reference
High Severity
| Detector | What It Finds | False Positive Risk |
|---|---|---|
reentrancy-eth |
Reentrancy with ETH transfer | Low — almost always real |
arbitrary-send-erc20 |
Unprotected transferFrom with user-controlled from |
Medium — check access control |
controlled-delegatecall |
delegatecall with user-controlled target | Low — critical if confirmed |
suicidal |
Contract can selfdestruct without protection | Low |
uninitialized-storage |
Storage variables used before initialization | Low |
arbitrary-send-eth |
ETH sent to arbitrary address | Medium — verify access control |
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 · 235 lines · 19 tokens per session scan A 715ee3f94e7e
slither-analyst is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 19 tokens to every session and 2,087 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
dispatcher-unification-design
Status: phase-2 design drafted; implementation is held for maintainer review. Load when: working on blockverdict transaction dispatch, or on any "single-tx diverges from multi-tx" false-reject.
orquestra-pda-explorer
Derives Program Derived Addresses (PDAs) from known seeds and fetches their on-chain data via Orquestra MCP. Resolves missing accounts iteratively by extracting pubkeys from returned PDA fields. Uses ONLY Orquestra MCP tools. Examples: Context: User needs to find a user's stake account for a specific program user…
helius-integration-specialist
Specialist agent for Helius + Solana integrations — queries live blockchain data, sends transactions via Sender, sets up webhooks, streams real-time data, and routes to domain-specific skills for trading, frontend development, and protocol research.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
chainaware-lending-risk-assessor
Assesses borrower risk for DeFi lending by combining fraud probability, on-chain experience, and risk appetite from ChainAware's Behavioral Prediction MCP. Returns a Borrower Risk Grade (A–F), a recommended collateral ratio, and an interest rate tier — so lending protocols can price risk per wallet rather than…
chainaware-sybil-detector
Screens a list of wallet addresses for Sybil attacks, coordinated voting fraud, and low-quality participation in DAO governance votes. Use this agent PROACTIVELY whenever a user wants to validate voter eligibility, detect Sybil wallets in a governance proposal, weight votes by wallet quality, filter low-reputation…