sprint-mcp: Instructions file for Claude Code

CLAUDE.md

sprint-mcp CLAUDE.md is an instructions file for Claude Code from cnavta/sprint-mcp. It costs 3,073 tokens per session, scanned A, original, MIT.

Repository instructions for Claude Code, an AI coding assistant, in a sprint-based software project. They explain the repository’s purpose, the order of authority among its instruction files, and the development workflow.

In plain words
What is it for?
Use them when Claude Code works in this repository and needs to plan, implement, validate, publish, or review sprint work according to the project’s rules.
Why use it?
They reduce conflicting instructions and help the assistant follow the project’s agreed process. They also clarify which file is the definitive source when guidance disagrees.

Instructions file for Claude Code

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

This is cnavta/sprint-mcp's own configuration. It tells Claude Code how to work on sprint-mcp 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 sprint-mcp configures →

Reuse

Borrowing it

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

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 sprint-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cnavta/sprint-mcp/claude-md.svg)](https://agentmods.dev/instructions/cnavta/sprint-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/cnavta/sprint-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/cnavta/sprint-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,073 This file is loaded in full into every session.
When invoked 3,073 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
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.03073 $0.03073
Opus 5 $0.01537 $0.01537
Sonnet 5 $0.00615 $0.00615
Haiku 4.5 $0.00307 $0.00307

Measured 6d ago against content hash 94d96ff57333, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

sprint-mcp CLAUDE.md scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

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

curl -X POST \
CLAUDE.md · 384 lines

How it starts

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

Repository Purpose

This is a sprint-based development repository governed by a strict LLM agent workflow protocol defined in AGENTS.md. The repository implements a structured sprint methodology where LLM agents execute development work through defined phases: Plan → Approve → Implement → Validate → Verify → Publish (PR) → Retro → Learn.

Critical Precedence Rules

Always consult these sources in order:

  1. architecture.yaml — canonical source of truth for system behavior (when it exists)
  2. AGENTS-uncompressed.md — operational and behavioral rules for agents (SOURCE FILE with explicit intent)
  3. AGENTS.md — semantically compressed version of AGENTS-uncompressed.md for token efficiency (DO NOT MODIFY)
  4. Everything else — examples, legacy docs, and supporting materials

If conflicts occur, architecture.yaml wins. Surface the conflict and align to it.

Protocol File Relationship

  • AGENTS-uncompressed.md: The SOURCE file for all protocol changes. Higher token count, more explicit intent. Always modify this file when updating the Sprint Protocol.
  • AGENTS.md: A semantically compressed version optimized for token efficiency. This is generated FROM AGENTS-uncompressed.md and should NOT be modified directly. Future sprints may need to recompress this file when AGENTS-uncompressed.md changes significantly.

Sprint Protocol Overview

Sprint Control Rules

  • S1: A sprint begins only when the user explicitly says "Start sprint"
  • S2: A sprint ends when validation criteria are satisfied OR documented exceptions are explicitly accepted, and the user says "Sprint complete" or "Force complete sprint"
  • S3: Only one sprint may be active at a time
  • S4: Prompts related to this repo are included in sprint scope unless specified otherwise
  • S5: If sprint state is unclear, ask once, then proceed with best judgment, but do not bypass explicit approval gates

Read the full file on GitHub · 384 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. 6d ago First seen · 384 lines · 3,073 tokens per session scan A 94d96ff57333

Subscribe to this mod's changes

sprint-mcp CLAUDE.md is an instructions file published in the GitHub repository cnavta/sprint-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 3,073 tokens to every session, about $0.0154 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

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

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

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

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

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