config: Instructions file for Claude Code

CLAUDE.md

config CLAUDE.md is an instructions file for Claude Code from SpineEventEngine/config. It costs 180 tokens per session, scanned A, original, Apache-2.0.

Project-specific instructions for the config repository of SpineEventEngine, where shared dependencies and build settings for subprojects are kept. They guide Claude Code on planning, task tracking, source-code discovery, and where to store team or personal notes.

In plain words
What is it for?
Use them when working on architecture changes, refactoring, documentation, Gradle-cached libraries, team instructions, or developer-specific notes in SpineEventEngine/config.
Why use it?
They reduce mistakes when changing a multi-project JVM codebase, especially around planning larger work and reading library code from Gradle's local cache. They also clarify which information belongs in the repository versus personal memory.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: names the ExitPlanMode tool; mentions Claude Code; mentions AGENTS.md.

This is SpineEventEngine/config's own configuration. It tells Claude Code how to work on config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything config configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SpineEventEngine/config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SpineEventEngine/config/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/SpineEventEngine/config

Made for: Claude Code.

Wrote 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.

agentmods badge for config CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/spineeventengine/config/claude-md/github.svg)](https://agentmods.dev/instructions/spineeventengine/config/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/spineeventengine/config/claude-md"><img src="https://agentmods.dev/badge/instructions/spineeventengine/config/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for config CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/spineeventengine/config/claude-md"><img src="https://agentmods.dev/badge/instructions/spineeventengine/config/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 180 This file is loaded in full into every session.
When invoked 180 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00180 $0.00180
Opus 5.5 $0.00072 $0.00072
Sonnet 5.5 $0.00036 $0.00036
Haiku 4.5 $0.00018 $0.00018

Measured 1mo ago against content hash 45dc81c13300, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

config 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 1mo 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.

CLAUDE.md · 17 lines

What it actually says

@AGENTS.md

Claude Code-specific notes

  • Use Plan mode (EnterPlanMode) for architecture, refactoring, multi-file changes, or lengthy documentation. Show the plan (ExitPlanMode) before implementing.
  • Track live progress with TaskCreate.
  • In JVM repos: before reading library source code from ~/.gradle/caches, follow the api-discovery skill — never unzip JARs directly.
  • Per-developer memory lives in the built-in auto-memory dir. Use it for personal preferences, ephemeral project state, and per-machine resources. Litmus test: would a teammate benefit from this next month? → repo. Otherwise → auto-memory.
  • This is living team memory. Update it regularly and keep it concise (<120 lines / ~2.5k tokens).
Changes

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.

  1. 1mo ago First seen · 17 lines · 180 tokens per session scan A 45dc81c13300

Subscribe to this mod's changes

config CLAUDE.md is an instructions file published in the GitHub repository SpineEventEngine/config (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 180 tokens to every session, about $0.0007 per session on Opus 5.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.

Related

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens