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 instructions/evmts/guillotine-mini/claude-mdgit clone --depth 1 https://github.com/evmts/guillotine-miniWrote 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/instructions/evmts/guillotine-mini/claude-md)<a href="https://agentmods.dev/instructions/evmts/guillotine-mini/claude-md"><img src="https://agentmods.dev/badge/instructions/evmts/guillotine-mini/claude-md.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 | $0.07337 | $0.07337 |
| Opus 5 | $0.03668 | $0.03668 |
| Sonnet 5 | $0.01467 | $0.01467 |
| Haiku 4.5 | $0.00734 | $0.00734 |
Grade A, and why
guillotine-mini CLAUDE.md 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 5d 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 — 771 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guillotine Mini - EVM Implementation
Minimal, correct, and well-tested Ethereum Virtual Machine (EVM) implementation in Zig, prioritizing specification compliance, clarity, and hardfork support (Berlin through Prague).
Quick Start
zig build # Build all modules
zig build test # Run unit + spec tests
zig build specs # Run ethereum/tests validation
zig build wasm # Build WebAssembly library
zig build test-watch # Interactive test runner
# Debug failing tests (recommended)
bun scripts/isolate-test.ts "test_name" # Max debug output + analysis
bun scripts/test-subset.ts "pattern" # Filter test categories
Prerequisites
- Zig 0.15.1+ (core build system)
- Cargo (required for BN254/ARK cryptographic dependencies)
- Python 3.8+ (test generation and reference implementation)
- uv (Python package manager for spec fixture generation):
brew install uv - Bun (TS helpers/agents):
brew install bun
Architecture
src/
├── evm.zig # Orchestrator: state, storage, gas refunds, nested calls
├── frame.zig # Bytecode interpreter: stack, memory, PC, per-opcode logic
├── host.zig # Abstract state backend interface
├── hardfork.zig # Hardfork detection and feature flags
├── opcode.zig # Opcode definitions and utilities
├── trace.zig # EIP-3155 trace generation
└── errors.zig # Error types
External Dependencies (fetched via zig build):
├── primitives # Ethereum types (Address, u256, gas constants, RLP, ABI, etc.)
│ # Source: https://github.com/evmts/primitives
├── crypto # Cryptographic primitives (keccak256, secp256k1, BLS12-381)
└── precompiles # Ethereum precompiled contracts
Core Responsibilities
| Component | Responsibility |
|---|---|
| Evm | State management, storage, gas refunds, warm/cold tracking, nested calls |
| Frame | Stack, memory, PC, bytecode interpretation, opcode execution |
| Host | Pluggable state backend (balances, nonces, code, logs, self-destruct) |
| Hardfork | Gas cost adjustments, feature flag guards (isAtLeast(), isBefore()) |
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.
- 5d ago First seen · 771 lines · 7,337 tokens per session scan A 2472c86089f7
guillotine-mini CLAUDE.md is an instructions file published in the GitHub repository evmts/guillotine-mini (10 stars, last pushed 1mo ago), licensed MIT. It adds 7,337 tokens to every session, about $0.0367 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-31.
Other instructions, from other repositories
evmole AGENTS.md
Instructions for cdump/evmole: EVMole extracts structured facts from deployed EVM runtime bytecode.
experiencer CLAUDE.md
Claude Code instructions for vincentlaucsb/experiencer: The canonical repository instructions are in AGENTS.md. Read and follow that file; this compatibility entrypoint intentionally defines no independent rules.
plamen CLAUDE.md
Claude Code instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.
pip-web CLAUDE.md
Claude Code instructions for playpip/pip-web, covering claude.md — agent guide for pip, read first (by task), the three layers (respect the boundaries), non-negotiables and commands / definition of done.
bitcoin-mcp copilot-instructions.md
Instructions for Bortlesboat/bitcoin-mcp, covering bitcoin-mcp copilot instructions, rules, satoshi api reference and verification.
kya-hub AGENTS.md
AGENTS.md instructions for UMBRAXON/kya-hub, covering agents.md — instructions for ai agents, 1. what kya-hub is, in one paragraph, 2. should you integrate?, 3. quickstart for an llm agent and 4. signing rules — the part that breaks everyone.