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.
curl -O https://raw.githubusercontent.com/Skowt/medusa/main/CLAUDE.mdgit clone --depth 1 https://github.com/Skowt/medusaWrote 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/skowt/medusa/claude-md)<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>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.1 | $0.10047 | $0.10047 |
| Opus 5 | $0.05024 | $0.05024 |
| Sonnet 5 | $0.02009 | $0.02009 |
| Haiku 4.5 | $0.01005 | $0.01005 |
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.
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:
make fmt— formats withgofmt+goimports.golangci-lint run— must exit 0. Run on just the touched package for speed (e.g.golangci-lint run ./internal/app/...).- No
.gofile may exceed 500 lines.make lintenforces this; if you hit it, split by concern into sibling files in the same package rather than inflating a single file. - Tests pass for the touched package.
- At the end of development, run
make lint— it mirrors CI by runninggo test -race -v ./...followed by golangci-lint and the 500-line check. The race detector catches issues plaingo testmisses (e.g. value-receiver methods likeWorkspace.Root()copy the whole struct, so a goroutine calling them races with any concurrent field write).make test-raceis 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.
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 Changed · +380 lines · +5,564 tokens per session 2a8ec4f68cef
- 7d ago First seen · 291 lines · 4,483 tokens per session scan A 6aaf080a2c6c
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.
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.
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).
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.
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).
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.