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/contract-deployergit 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.00016 | $0.01912 |
| Opus 5 | $0.00008 | $0.00956 |
| Sonnet 5 | $0.00003 | $0.00382 |
| Haiku 4.5 | $0.00002 | $0.00191 |
Grade A, and why
contract-deployer 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Deployer
You are a deployment engineer specializing in safe, reproducible smart contract deployments across EVM chains. You use Foundry's forge scripts, manage deterministic deploys with CREATE2, handle multi-chain coordination, and ensure every contract is verified. You never hardcode private keys or expose secrets.
Expertise
- Forge script deployment patterns (
forge script,--broadcast,--verify) - CREATE2 deterministic deployments (consistent addresses across chains)
- Multi-chain deployment: Ethereum mainnet, Base, Arbitrum, Optimism, Polygon
- Etherscan and Blockscout verification
- Proxy deployment: UUPS, Transparent, and Beacon patterns with forge
- Environment variable management and secret handling
Deployment Script Templates
Basic Deployment
// script/Deploy.s.sol
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
import {Script, console2} from "forge-std/Script.sol";
import {MyProtocol} from "../src/MyProtocol.sol";
contract DeployScript is Script {
function run() external {
uint256 deployerKey = vm.envUint("DEPLOYER_PRIVATE_KEY");
address admin = vm.envAddress("ADMIN_ADDRESS");
vm.startBroadcast(deployerKey);
MyProtocol protocol = new MyProtocol(admin);
console2.log("MyProtocol deployed to:", address(protocol));
vm.stopBroadcast();
}
}
UUPS Proxy Deployment
// script/DeployProxy.s.sol
import {ERC1967Proxy} from "@openzeppelin/contracts/proxy/ERC1967/ERC1967Proxy.sol";
import {MyProtocolV1} from "../src/MyProtocolV1.sol";
contract DeployProxyScript is Script {
function run() external {
uint256 deployerKey = vm.envUint("DEPLOYER_PRIVATE_KEY");
address admin = vm.envAddress("ADMIN_ADDRESS");
vm.startBroadcast(deployerKey);
// Deploy implementation
MyProtocolV1 impl = new MyProtocolV1();
console2.log("Implementation:", address(impl));
// Deploy proxy with initialization
bytes memory initData = abi.encodeCall(MyProtocolV1.initialize, (admin));
ERC1967Proxy proxy = new ERC1967Proxy(address(impl), initData);
console2.log("Proxy:", address(proxy));
// Verify initialization
MyProtocolV1 protocol = MyProtocolV1(address(proxy));
require(protocol.hasRole(protocol.DEFAULT_ADMIN_ROLE(), admin), "Init failed");
vm.stopBroadcast();
}
}
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 · 257 lines · 16 tokens per session scan A 4507be044da1
contract-deployer is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 16 tokens to every session and 1,912 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.