Borrowing it
Nothing to install: this file belongs to MarioEpkOne/PipelineIQ. 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/MarioEpkOne/PipelineIQ/main/CLAUDE.mdgit clone --depth 1 https://github.com/MarioEpkOne/PipelineIQWrote 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/marioepkone/pipelineiq/claude-md)<a href="https://agentmods.dev/instructions/marioepkone/pipelineiq/claude-md"><img src="https://agentmods.dev/badge/instructions/marioepkone/pipelineiq/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/marioepkone/pipelineiq/claude-md"><img src="https://agentmods.dev/badge/instructions/marioepkone/pipelineiq/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.02282 | $0.02282 |
| Opus 5 | $0.01141 | $0.01141 |
| Sonnet 5 | $0.00456 | $0.00456 |
| Haiku 4.5 | $0.00228 | $0.00228 |
Grade A, and why
PipelineIQ 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PipelineIQ — Context for Claude
What this project does
Claude Code slash commands that form a closed-loop spec → plan → implement → audit → fix → merge pipeline. Not a library or app — the deliverables are markdown prompt files in commands/ that Claude Code executes as slash commands. There is no build step, no test suite, and no runtime beyond Claude Code itself.
Invariants
- Artifact directories are never inside worktrees.
specs/,Implementation Plans/,Working Logs/,learnings.md, andpromotion-log.mdexist only in the main repo root. Subagent reference files use[MASTER_REPO_PATH]to write there — if a subagent writes an artifact relative to the worktree, the pipeline's next phase won't find it. specs/is an inbox;specs/applied/is an archive;specs/team/is the batch-ready staging area. A spec moves toapplied/only afterimpl-plansaves a plan for it (or after/spec-splittergenerates children from it).pipeline-teamdiscovers pending work by listingspecs/team/by default (or an explicit directory via argument). Moving a spec prematurely makes it invisible to the batch runner.references/files are subagent prompt templates, not documentation. Each pipeline phase reads its reference file at runtime and fills[VARIABLES]. Renaming, moving, or reformatting a reference file breaks the phase that loads it — the pre-flight check inpipeline.mdvalidates all 13 exist (7 reference files + 6 agent definitions) before starting.learnings.mdis append-only during pipeline runs. Pipeline Phase 6 appends entries; it never deletes or rewrites existing ones./learnings-reviewis the only process that modifies existing entries.[COMMANDS_PATH]is resolved dynamically at pipeline startup. No absolute user paths exist in any command file.pipeline.mdandpipeline-team.mdeach resolve COMMANDS_PATH via installed_plugins.json registry lookup (with CWD ancestry walk fallback) before pre-flight checks, then pass it to all subagent prompts as a bracket variable.- Agent definition invariant sync. If you modify invariants in this file, check whether any agent definitions in
agents/embed the same invariant and update them to match. Currently, agents embed: artifact directory rules, worktree commit hook caveat, audit->fix handoff contract, and project KB read instructions. - Per-agent project KB files are read-only during pipeline runs. Pipeline subagents read
.claude/pipeline-kb/<agent>.mdfrom the target project but never modify them. Only/learnings-reviewwrites to KB files.
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.
- 9d ago First seen · 63 lines · 2,282 tokens per session scan A c3fca1c5ab3b
PipelineIQ CLAUDE.md is an instructions file published in the GitHub repository MarioEpkOne/PipelineIQ (2 stars, last pushed 3mo ago), licensed MIT. It adds 2,282 tokens to every session, about $0.0114 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
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.