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/wakehacker/wake-ai/claude-mdgit clone --depth 1 https://github.com/wakehacker/wake-aiWrote 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/wakehacker/wake-ai/claude-md)<a href="https://agentmods.dev/instructions/wakehacker/wake-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/wakehacker/wake-ai/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.02045 | $0.02045 |
| Opus 5 | $0.01022 | $0.01022 |
| Sonnet 5 | $0.00409 | $0.00409 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
wake-ai 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 3d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wake AI Architecture
Overview
Wake AI is now a standalone Python package that provides AI-powered smart contract analysis capabilities. It has been extracted from the Wake framework into an independent module that can be used separately or integrated with other tools.
Module Structure
The project is organized into two main directories:
1. Core Framework (wake_ai/)
Contains the AI framework implementation:
- core/ - Core Claude integration and workflow engine
claude.py- Claude Code CLI wrapper with session managementflow.py- Base workflow and step classesexceptions.py- Custom exceptionsutils.py- Framework utilities
- detections.py - Detection data models and formatters
- results.py - Result types (AIResult, SimpleResult, AIDetectionResult)
- runner.py - Workflow execution helper
- utils.py - Shared utilities (YAML loading, validation)
- cli.py - Command-line interface
2. Workflows (flows/)
Contains pre-built workflow implementations:
- audit/ - Comprehensive security audit workflow
- uniswap_detector.py - Uniswap-specific detector
3. Examples (examples/)
Contains educational example workflows:
- reentrancy/ - Reentrancy detection workflow
- reentrancy_test/ - Reentrancy testing workflow
- hooks/ - Hook example workflow
Key Features
Standalone CLI
Wake AI provides its own CLI interface:
wake-ai --flow audit # Run audit workflow
wake-ai --flow audit -s contracts/*.sol # Audit specific files
wake-ai --resume # Resume previous session
wake-ai --export results.json # Export results
Session Management
- Each workflow creates its own
ClaudeCodeSession - Sessions can be resumed between runs
- Working directory isolation per session
- State persistence for interrupted workflows
Cost Management
query_with_cost()implements intelligent cost-limited execution- Configurable cost limits per step
- Automatic prompt optimization when approaching limits
- Cost tracking and reporting
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.
- 3d ago First seen · 284 lines · 2,045 tokens per session scan A 0fbe87bf6f47
wake-ai CLAUDE.md is an instructions file published in the GitHub repository wakehacker/wake-ai (21 stars, last pushed 5mo ago), licensed ISC. It adds 2,045 tokens to every session, about $0.0102 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.