What is sprint-mcp AGENTS.md?

Repository instructions defining a human–LLM sprint protocol for software development. They describe who makes decisions, how work is approved, and which instruction source takes precedence.

Use them when an AI assistant works in this repository and must plan, implement, validate, document, or release sprint work within the stated responsibilities.

They prevent an AI coding assistant from making decisions reserved for a human, such as approving scope or releasing software. They also provide a clear process for planning and recording work.

How cnavta/sprint-mcp configures Codex and OpenCode

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/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/cnavta/sprint-mcp

Made for: Codex, OpenCode.

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/cnavta/sprint-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/cnavta/sprint-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/cnavta/sprint-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/cnavta/sprint-mcp/agents-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/cnavta/sprint-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/cnavta/sprint-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7,336 This file is loaded in full into every session.

When invoked 7,336 The same file — it is already loaded in full.

Security scan B 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.07336	$0.07336
Opus 5.5	$0.02934	$0.02934
Sonnet 5.5	$0.01467	$0.01467
Haiku 4.5	$0.00734	$0.00734

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

Security

Grade B, and why

sprint-mcp AGENTS.md scanned grade B 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 2mo 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

curl -X POST "$SLACK_WEBHOOK" -d "{\"text\": \"Sprint $SPRINT_ID completed!\"}"

Makes network callslowCapability

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

curl -X POST "$SLACK_WEBHOOK" -d "{\"text\": \"Sprint $SPRINT_ID completed!\"}"

AGENTS.md · 894 lines

How it starts

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

AGENTS.md — Human–LLM Sprint Protocol v3.0

0. Precedence & Scope

Human–LLM partnership rules for this repository. Human: intent, judgment, approvals, exceptions, releases. LLM: plans, implementation, validation, Git history.

Precedence Order:

architecture.yaml — canonical source of truth
AGENTS.md — operational rules
Everything else

Conflict resolution: architecture.yaml wins. Surface conflict, then align.

Partnership Authority

Human MUST:

Set/approve sprint intent and scope
Approve execution plan before implementation
Decide exception acceptance
Declare sprint complete or force-complete
Make and execute all release decisions

LLM allowed:

Execute shell commands
Git operations (checkout, branch, commit, push)
Create/push feature branches
Create PR only when human explicitly assigns
Run non-mutating release dry runs when approved

LLM MUST:

Record sprint-relevant turns in request-log.md
Record shell/Git operations when they change state or provide evidence
Operate within provided repository
Halt and request credentials if auth fails
Report results transparently
Preserve human decision points

LLM MUST NOT:

Execute real/mutating release commands
Create/push release tags
Publish packages/deployments/releases

1. Immutable Laws

Partnership: Ask for human judgment when authority/intent required; proceed autonomously within approved scope
Never violate architecture.yaml: Suggest changes with justification only
All sprint artifacts live in ./planning
Never use ./deprecated in deliverables: Read for context only, never import/execute/copy/depend
./preview is directional only, not implementation-ready
Release is human task: LLM prepares evidence/recommendations, MUST NOT execute real release
Executable intent: Everything traceable, reproducible, reversible

2. Human–LLM Sprint Protocol

Frame → Plan → Approve → Implement + Commit
  ↳ Follow-Up: Stop → Clarify → Append → Continue
  ↳ PR: Human | LLM | Automation (when approved)
  → Validate + Verify → Retro + Learn → Push Handoff
  → Human Complete → Human Release (optional)

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

2mo ago First seen · 894 lines · 7,336 tokens per session scan B 85c75a6e3461

Subscribe to this mod's changes

sprint-mcp AGENTS.md is an instructions file published in the GitHub repository cnavta/sprint-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 7,336 tokens to every session, about $0.0293 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning agentic-workflow ai ai-agents coding-agents sprint-management workflow

sprint-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sprint-mcp AGENTS.mdcnavta/sprint-mcp	Instructions file	1	2mo ago	MIT	B	7,336	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	3d ago	MIT	A	4,313	Codex, OpenCode

sprint-mcp: Instructions file for Codex