Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/CLAUDE.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/claude-md)<a href="https://agentmods.dev/instructions/theastrelo/claude-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/theastrelo/claude-pipeline/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/theastrelo/claude-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/theastrelo/claude-pipeline/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.04731 | $0.04731 |
| Opus 5 | $0.02365 | $0.02365 |
| Sonnet 5 | $0.00946 | $0.00946 |
| Haiku 4.5 | $0.00473 | $0.00473 |
Grade A, and why
Claude-Pipeline 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 10d 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 — 347 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.
Project Overview
This is a provider-agnostic 13-phase (0–12) development pipeline for Claude Code
and Codex. It transforms a task description into reviewed, optionally committed
code. The single engine is run-pipeline.sh.
The One Engine
run-pipeline.sh is the single real executable. It runs each phase as a fresh
claude -p --no-session-persistence or codex exec --ephemeral subprocess,
persists and validates the returned report, applies the gate, and optionally
commits after Phase 12.
run-pipeline.sh— the engine. Run it directly:bash run-pipeline.sh [options] "task"..claude/commands/auto-pipeline.md— a thin/auto-pipelineslash-command wrapper that runs the engine withPIPELINE_NONINTERACTIVE=1and interprets its exit code.- The per-phase slash commands (
/design,/plan-review,/ar,/security-review, …) are interactive helpers that dispatch to.claude/agents/via the Task tool. The engine does not use them — it builds every phase prompt inline inbuild_prompt().
Commands
# Run the pipeline (standalone)
bash run-pipeline.sh "add a GET /api/version endpoint"
bash run-pipeline.sh --provider=codex "add a GET /api/version endpoint"
bash run-pipeline.sh --provider=claude "add a GET /api/version endpoint"
bash run-pipeline.sh --profile=paranoid --mode=dev "handle payments"
# Demo starter project (demo/starter-project/)
npm install && npm test
# Full test battery (one command; auto-discovers every tests/*.sh suite)
bash tests/run-all.sh # sequential
bash tests/run-all.sh -p # parallel
Flags the engine actually parses: --provider=auto|claude|codex,
--profile=yolo|fast|standard|paranoid, --mode=auto|dev, --push
(publish the committed run branch to the remote), --pr (--push plus
pull-request guidance), --budget=elastic|strict,
--skip-arm (skip Phase 1), --skip-ar (skip Phase 3), --skip-pmatch (skip Phase 5),
--model-strong=, --model-fast=, --max-budget-usd= (per-phase cap), --max-run-budget-usd=
(whole-run cap), --no-commit, --allow-dirty, --allow-untested-commit
(explicit recorded no-test auto-commit waiver), --resume=RUN_ID,
--policy-rollout=legacy|shadow|enforced, --retention-days=,
--retention-max-runs=, --help.
Env knobs: PIPELINE_PROVIDER_TIMEOUT_SECONDS (default 2400),
PIPELINE_PROVIDER_RETRIES (default 1), PIPELINE_AUTH_PREFLIGHT=0,
PIPELINE_BASELINE_CHECKS=0, PIPELINE_COMMAND_TIMEOUT_SECONDS (default 900),
PIPELINE_WORKTREE=0 (legacy in-place mode), PIPELINE_WORKTREE_LINK_PATHS
(gitignored build state symlinked into the run worktree; default
node_modules .venv venv vendor), PIPELINE_ALLOW_REMOTE_DEPS=1 (recorded
waiver for git/https dependency specifiers), --budget=elastic|strict /
PIPELINE_BUDGET_POLICY (elastic default: a capped phase retries with a
doubled cap within the run cap, ledger-recorded; budgets are excluded from
the resume identity so a run-cap halt resumes with a higher cap),
PIPELINE_BUDGET_EXTENSIONS (default 2), PIPELINE_COLLAPSE=0 (full
planning ladder in yolo/fast), PIPELINE_BUILD_FIX_ATTEMPTS (default 2;
in-build verify/fix loop, 0 disables).
PIPELINE_PUSH_REMOTE (default origin).
Resume requires the original task and an exact engine/config/Git/evidence
match. Still not implemented: --template, --batch-qa, --fix, and a
--yolo shorthand.
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.
- 10d ago First seen · 347 lines · 4,731 tokens per session scan A 3b78f76cc373
Claude-Pipeline CLAUDE.md is an instructions file published in the GitHub repository TheAstrelo/Claude-Pipeline (45 stars, last pushed 5d ago), licensed MIT. It adds 4,731 tokens to every session, about $0.0237 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-30.
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.
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.
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).
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).
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.
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.