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/erupts/erupt/claude-mdgit clone --depth 1 https://github.com/erupts/eruptWrote 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/erupts/erupt/claude-md)<a href="https://agentmods.dev/instructions/erupts/erupt/claude-md"><img src="https://agentmods.dev/badge/instructions/erupts/erupt/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.02062 | $0.02062 |
| Opus 5 | $0.01031 | $0.01031 |
| Sonnet 5 | $0.00412 | $0.00412 |
| Haiku 4.5 | $0.00206 | $0.00206 |
Grade A, and why
erupt 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 4d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Test Commands
# Build entire project
mvn clean install
# Build a single module (and its dependencies)
mvn clean install -pl erupt-core -am
# Skip tests for faster builds
mvn clean install -DskipTests
# Run all tests (erupt-test module uses H2 in-memory DB)
mvn test -pl erupt-test
# Run a specific test class
mvn test -pl erupt-test -Dtest=LambdaQueryTest
# Run a specific test method
mvn test -pl erupt-test -Dtest=LambdaQueryTest#lambdaQueryTest
# Run the sample application for local testing
cd erupt-sample && mvn spring-boot:run
# Publish to Maven Central (GPG signing, Javadoc; wraps `mvn clean deploy -P release`)
./scripts/deploy.sh
# Bump version across this repo AND satellite repos (erupt-web etc.)
./scripts/bump-erupt.sh [--dry-run] x.x.x
Java 17 required. Spring Boot 3.5.x (pinned via spring.boot.version in the parent pom). No Maven wrapper — use system mvn.
Architecture Overview
Erupt is a low-code platform framework that auto-generates admin UIs from Java annotations, with zero frontend code required.
Module Structure
The project is a multi-module Maven project (~50 modules):
| Group | Modules |
|---|---|
| Core | erupt-annotation (annotation declarations), erupt-core (runtime engine) |
| Data | erupt-data/erupt-data-{jpa,mongodb,memory,http,jdbc,es,ldap,k8s,s3,redis,file,feishu,notion} — JPA is the default; the rest are pluggable connectors |
| Platform | erupt-upms (user/permissions), erupt-security, erupt-admin, erupt-web (frontend assets) |
| Starter | erupt-starter/{erupt-spring-boot-starter,erupt-spring-boot-starter-all} |
| Templates | erupt-tpl/erupt-tpl (engine) + erupt-tpl/{ant-design,element-ui,element-plus,amis} (skins) |
| AI | erupt-ai/{erupt-ai,erupt-ai-canvas,erupt-ai-claw,erupt-ai-staff,erupt-ai-rag} (LLM + MCP via langchain4j; RAG knowledge base with Qdrant/Milvus) |
| Support | erupt-support/{erupt-toolkit,erupt-excel,erupt-websocket} (shared capabilities: cache/notify, import/export, realtime transport) |
| Plugin | erupt-plugin/{erupt-report,erupt-designer,erupt-job,erupt-generator,erupt-monitor,erupt-magic-api,erupt-notice,erupt-print,erupt-terminal} |
| Cloud | erupt-cloud/{erupt-cloud-common,erupt-cloud-server,erupt-cloud-node,erupt-cloud-node-jpa} |
| Deploy | erupt-deploy/erupt-docker (all-in-one Docker image; has its own deploy.sh) |
| Dev | erupt-test (JUnit 5 + H2), erupt-sample (runnable demo) |
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.
- 4d ago First seen · 139 lines · 2,062 tokens per session scan A 8ec7685e420c
erupt CLAUDE.md is an instructions file published in the GitHub repository erupts/erupt (2,767 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,062 tokens to every session, about $0.0103 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
prest copilot-instructions.md
Copilot instructions for prest/prest, covering copilot instructions for prest go backend, project scope, core engineering principles, solid principles for go and s — single responsibility.
astron-agent AGENTS.md
AGENTS.md instructions for iflytek/astron-agent, covering agents.md, project overview, repository structure, console and core microservices.
ck CLAUDE.md
Claude Code instructions for BeaconBay/ck, covering claude development guide, release process, version tagging convention, correct format (current standard since 0.3.8+) and old format (deprecated, do not use).
nocobase AGENTS.md
AGENTS.md instructions for nocobase/nocobase, covering agents, personal local rules, project structure, code style rules and database & migrations.
windmill AGENTS.md
AGENTS.md instructions for windmill-labs/windmill, covering windmill, workflow, documentation, dev environment and per-worktree ports and database.
easy-vibe CLAUDE.md
Claude Code instructions for datawhalechina/easy-vibe, covering claude.md, project overview, development commands, start local documentation server and build/run commands.