Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/blakemartz/delivery-loop/claude-mdgit clone --depth 1 https://github.com/blakemartz/delivery-loopWhat 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 | $0.02076 | $0.02076 |
| Opus 5 | $0.01038 | $0.01038 |
| Sonnet 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 2d 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.
- 2d 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 (4 stars, last pushed 1mo ago), licensed MIT. It adds 2,076 tokens to every session, about $0.0104 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
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
platform CLAUDE.md
Instructions for ambient-code/platform, covering ambient code platform, structure, key files, session flow and commands.
autogen copilot-instructions.md
Copilot instructions for microsoft/autogen, covering autogen multi-agent ai framework, working effectively, prerequisites and environment setup, python development workflow and quick validation (under 1 second each).
toh-framework CLAUDE.md
Instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).