Borrowing it
Nothing to install: this file belongs to blakemartz/delivery-loop. 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/blakemartz/delivery-loop/main/CLAUDE.mdgit clone --depth 1 https://github.com/blakemartz/delivery-loopWrote 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/blakemartz/delivery-loop/claude-md)<a href="https://agentmods.dev/instructions/blakemartz/delivery-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/blakemartz/delivery-loop/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.
<a href="https://agentmods.dev/instructions/blakemartz/delivery-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/blakemartz/delivery-loop/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02076 | $0.02076 |
| Opus 5.5 | $0.00830 | $0.00830 |
| Sonnet 5.5 | $0.00415 | $0.00415 |
| Haiku 4.5 | $0.00208 | $0.00208 |
Grade A, and why
delivery-loop 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 1mo 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code working on this repository. This repo is the
delivery-loop plugin — you are editing a shareable package. It also dogfoods
the loop on itself (see "Dogfooding"), so you may additionally be running
the loop here. For how the loop works and how a consumer uses it, read
README.md; don't duplicate it here.
What this is
A self-contained agentic software-delivery loop for Claude Code, shipped as a
plugin + marketplace. Consumers write specs; the loop files them as a
GitHub-Issues backlog, then agents claim → implement → adversarially review →
patch → merge each task in its own git worktree, behind one per-repo correctness
gate. There is no server and no database — state is the consumer's repo, its
Issues, and gh + git + jq.
The system was extracted and generalized from the Lineage monorepo, where it runs live. Lineage is upstream: most changes originate there and get ported here (see "Origin & sync"). This repo is the generic, redistributable copy.
The cardinal rule: everything must stay repo-agnostic
Every skill and script here runs inside someone else's repo. The single most common way to break this package is to leak specifics of one consumer.
- No consumer-specific strings. No
lineage, no hardcoded tool names (pnpm,uv,alembic,afplay), no assumed filenames (CLAUDE.md, a specific spec name). If you're tempted to write one, route it through config instead. Quick check:grep -ri lineage plugins/must stay empty. - Per-repo behavior lives in exactly one place:
.claude/delivery.confin the consumer's repo, resolved byscripts/lib/config.sh. Skills read config keys (GATE_CMD,SPEC_SOURCES, …); they never name a concrete command. - Scripts self-reference via
${CLAUDE_PLUGIN_ROOT}so they resolve wherever the plugin is installed. Never use paths relative to a checkout. - Docs are cited by section number. Skills reference
docs/agentic_delivery_spec.md §N. When editing those docs, preserve existing§numbers so the citations keep resolving.
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.
- 1mo ago First seen · 160 lines · 2,076 tokens per session scan A 2b4e53ea401d
delivery-loop CLAUDE.md is an instructions file published in the GitHub repository blakemartz/delivery-loop (5 stars, last pushed 3mo ago), licensed MIT. It adds 2,076 tokens to every session, about $0.0083 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.