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/agents/README.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/agents/theastrelo/claude-pipeline/readme)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/readme"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/readme.svg" alt="Measured on agentmods" 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.00000 | $0.00209 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
README 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 8d 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.
What it actually says
Interactive agents (helpers, not the engine)
These agents back the per-phase slash commands (/design, /ar,
/security-review, …) when you run them interactively in Claude Code. The
pipeline engine (run-pipeline.sh) does not use them — it inlines every
phase prompt in build_prompt(). Editing an agent changes the interactive
helper only, never engine behavior.
Reference-project content. Several of these prompts were written for the
specific app the pipeline was extracted from (a Next.js + PostgreSQL SaaS
called "RDO") and still name its tables, imports, and UI conventions as
examples. Treat those as illustrations of shape, not rules for your
project. Your real conventions belong in .claude/rules/*.md
(see examples/reference-project-rules/ for a worked example). If you copy
.claude/ into another project and use these agents interactively, adjust
the project-specific references first.
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.
- 8d ago First seen · 17 lines · 0 tokens per session scan A e411f7a301df
README is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 209 tokens. 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 agents, from other repositories
spec-fidelity-auditor
Conformance of a change to its own specification (ticket, acceptance criteria, spec KB, solution plan, resolved decisions): a per-change requirements-traceability matrix swept both ways. Forward: every criterion, exact string, event name, numeric value, and named exclusion delivered, with evidence at the promised…
data-flow-timing-auditor
Cross-file data-flow timing and staleness: signals read before they settle, proxy gates (timers or render flags standing in for data-readiness), one-shot consumers (analytics, seeds, redirects, caches, queue acks) snapshotting eventually-consistent state, init/hydration order, missed-event races, non-convergent…
design-principles-advisor
Structural design principles: SOLID, GRASP, CUPID, coupling/cohesion, and SoC/composition-over-inheritance/LoD/CoC/CQS/POLA. Two gates: PLAN (shape a sound design) and VERIFY (audit a design or diff). Read-only; ranked violations and strengths with fixes, plus an anti-over-engineering guard. Not…
developer-reviewer
Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…
accessibility-auditor
Accessibility of an implemented UI in code, on the axes a linter cannot reach: the keyboard-only path, focus management and focus visibility, accessible names and labels, semantics and roles (native element first, ARIA only to fill a gap), dialog and overlay behaviour (focus trap, restore, escape, scroll lock)…
compatibility-auditor
Whether a change breaks an existing consumer, and whether the PR's breaking-change assertion is true. Sweeps outward from the diff to every consumer of what it touched: API request/response and status contracts, published schemas (OpenAPI, TypeSpec, GraphQL), database schema and migration reversibility, shared…