medusa: Instructions file for Claude Code

CLAUDE.md

medusa CLAUDE.md is an instructions file for Claude Code, Codex from Skowt/medusa. It costs 10,047 tokens per session, scanned A, original, MIT.

A set of instructions for coding agents working on the Medusa Go repository. It explains the project’s architecture, common commands, and the checks required before a Go change is considered complete.

In plain words
What is it for?
Use it when making changes to Medusa, especially Go code under internal/app. It guides building, formatting, targeted tests, race-detector runs, linting, and final CI-like verification.
Why use it?
It gives contributors a shared definition of done and reduces missed formatting, lint, testing, race-condition, and file-size checks. It also documents important repository-specific behavior and commands.

Instructions file for Claude CodeCodex

Written for Claude Code and Codex: SubagentStop hook event, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

This is Skowt/medusa's own configuration. It tells Claude Code and Codex how to work on medusa 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 medusa configures →

View source ↗ Skowt/medusa
Reuse

Borrowing it

Nothing to install: this file belongs to Skowt/medusa. 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/Skowt/medusa/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Skowt/medusa

Made for: Claude Code, Codex.

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 medusa CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/skowt/medusa/claude-md.svg)](https://agentmods.dev/instructions/skowt/medusa/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/skowt/medusa/claude-md"><img src="https://agentmods.dev/badge/instructions/skowt/medusa/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 10,047 This file is loaded in full into every session.
When invoked 10,047 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.10047 $0.10047
Opus 5 $0.05024 $0.05024
Sonnet 5 $0.02009 $0.02009
Haiku 4.5 $0.01005 $0.01005

Measured 3d ago against content hash 2a8ec4f68cef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

CLAUDE.md · 671 lines

How it starts

The opening of the file, as written. The whole thing — 671 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.

Definition of done

Before declaring any Go change complete:

  1. make fmt — formats with gofmt + goimports.
  2. golangci-lint run — must exit 0. Run on just the touched package for speed (e.g. golangci-lint run ./internal/app/...).
  3. No .go file may exceed 500 lines. make lint enforces this; if you hit it, split by concern into sibling files in the same package rather than inflating a single file.
  4. Tests pass for the touched package.
  5. At the end of development, run make lint — it mirrors CI by running go test -race -v ./... followed by golangci-lint and the 500-line check. The race detector catches issues plain go test misses (e.g. value-receiver methods like Workspace.Root() copy the whole struct, so a goroutine calling them races with any concurrent field write). make test-race is the same race run without lint, handy for reproducing a CI failure in isolation.

Don't batch these up for a later cleanup pass — fix as you go.

Common commands

make build            # builds `medusa` and `medusa-hook-emit`
make run              # build + run the TUI
make dev              # hot-reload via air
make test             # go test -v ./...
make test-race        # go test -race -v ./... (mirrors CI; slower)
make lint             # full gate: test-race + golangci-lint + 500-line check
make fmt              # gofmt + goimports
make bench            # compositor render benchmarks

Run a single test:

go test ./internal/app -run TestCopyIgnoredFiles -v

Headless render/perf harness (no human, no terminal):

go run ./cmd/medusa-harness -mode monitor -frames 5 -warmup 1
go run ./cmd/medusa-harness -mode center  -frames 5 -warmup 1
go run ./cmd/medusa-harness -mode sidebar -frames 5 -warmup 1

release-check runs tests + all three harness modes — use it to validate UI-adjacent changes without a real terminal.

Read the full file on GitHub · 671 lines

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. 3d ago Changed · +380 lines · +5,564 tokens per session 2a8ec4f68cef
  2. 7d ago First seen · 291 lines · 4,483 tokens per session scan A 6aaf080a2c6c

Subscribe to this mod's changes

medusa CLAUDE.md is an instructions file published in the GitHub repository Skowt/medusa (5 stars, last pushed 7d ago), licensed MIT. It adds 10,047 tokens to every session, about $0.0502 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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 · 6,785 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,296 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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens