What is lyra-mcp-server CLAUDE.md?

A project instruction file for Claude working on the Lyra MCP server. It defines preparation steps, testing requirements, Jira tracking, and rules for working safely in parallel.

Use it when modifying the Lyra MCP server, especially for work involving Jira, shared repositories, parallel sessions, or changes that must stay synchronized.

It prevents untracked or conflicting changes and ensures architecture, existing work, and tests are checked before and after development.

How luisa-sys/lyra-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to luisa-sys/lyra-mcp-server. 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/luisa-sys/lyra-mcp-server/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/luisa-sys/lyra-mcp-server

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/luisa-sys/lyra-mcp-server/claude-md/github.svg)](https://agentmods.dev/instructions/luisa-sys/lyra-mcp-server/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/luisa-sys/lyra-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/luisa-sys/lyra-mcp-server/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/luisa-sys/lyra-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/luisa-sys/lyra-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5,899 This file is loaded in full into every session.

When invoked 5,899 The same file — it is already loaded in full.

Security scan C 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.05899	$0.05899
Opus 5.5	$0.02360	$0.02360
Sonnet 5.5	$0.01180	$0.01180
Haiku 4.5	$0.00590	$0.00590

Measured 12d ago against content hash cd621af83843, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

lyra-mcp-server CLAUDE.md scanned grade C with 2 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 12d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

**Cleanup is mandatory at end of session:** every worktree Claude created must be either removed (work merged or abandoned) or explicitly noted as "kept for next session" in the session summary. Use `git worktree remove

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://mcp.checklyra.com/.well-known/mcp.json | jq -r .build_sha

CLAUDE.md · 253 lines

How it starts

The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — Project Instructions for Claude

This file contains instructions and policies that Claude must follow when working on this repository.

Pre-Work Checklist

Before starting any task, Claude must:

Check Jira — confirm a ticket exists for the work, or create one. Never start work without a tracked ticket.
Check the lyra repo's docs/ — architecture docs live in the main lyra repo at docs/. Read relevant docs before acting on architecture, ops, or infrastructure questions.
Check for existing work — search the codebase and recent PRs to avoid duplicating effort.
Run tests before and after — every change must leave tests green.
Confirm working tree isolation — if any other Claude Code instance might be running against this repo, this session MUST run inside its own git worktree (see "Parallel Claude sessions" below). Verify with git branch --show-current at the start of work AND right before every commit; if HEAD has changed unexpectedly, stop and recover (BUGS-17).

Parallel Claude sessions — use git worktrees

Luisa runs multiple Claude Code instances in parallel to work on independent features. All instances after the first MUST operate in a git worktree rather than the shared main checkout. Without isolation, parallel processes switch HEAD mid-flow and contaminate each other's commits — see BUGS-17 for the canonical incident (KAN-69a work landed on top of KAN-191 commits because two Claude sessions were sharing one checkout).

The lyra repo's CLAUDE.md is the source of truth for this policy. Briefly:

Use EnterWorktree (Claude Code built-in) to isolate the current session.
For sub-agents, pass isolation: "worktree" on the Agent tool call.
For manually-launched sessions, git worktree add ../<repo>-<branch> origin/main (or origin/develop in the lyra repo) before invoking claude.
Pre-commit safety check: git branch --show-current must equal the branch you intended. If it doesn't, do not commit — recover per BUGS-17's recovery section.

Read the full file on GitHub · 253 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.

12d ago Changed · +412 tokens per session cd621af83843
28d ago Changed · -13 lines · -89 tokens per session 890e4240edee
2mo ago First seen · 266 lines · 5,576 tokens per session scan C 5e0bf97a606a

Subscribe to this mod's changes

lyra-mcp-server CLAUDE.md is an instructions file published in the GitHub repository luisa-sys/lyra-mcp-server (0 stars, last pushed 5d ago), licensed MIT. It adds 5,899 tokens to every session, about $0.0236 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Project management

lyra-mcp-server CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lyra-mcp-server CLAUDE.mdluisa-sys/lyra-mcp-server	Instructions file	0	5d ago	MIT	C	5,899	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

lyra-mcp-server: Instructions file for Claude Code