Borrowing it
Nothing to install: this file belongs to SpaiR/task-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/SpaiR/task-pipeline/main/CLAUDE.mdgit clone --depth 1 https://github.com/SpaiR/task-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/spair/task-pipeline/claude-md)<a href="https://agentmods.dev/instructions/spair/task-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/spair/task-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/spair/task-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/spair/task-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.02343 | $0.02343 |
| Opus 5.5 | $0.00937 | $0.00937 |
| Sonnet 5.5 | $0.00469 | $0.00469 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
task-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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when editing this repository. User docs are the website/ site, which owns usage prose, and README.md. The contract is docs/contract.md; read the section a rule links before a non-trivial edit. Path-specific how-to in .claude/rules/ loads when you read a matching file.
Where a rule lives. Every rule a /self-audit lens enforces, and every irreversible one (CHANGELOG, version, commits), stays here as a one-liner linking the contract section that holds its full statement and the why. .claude/rules/ holds path-specific how-to only.
Quick orient
The task plugin: five skills implementing a chat-first context-serialization protocol, not an orchestration engine. One skill fixes a chat discussion into a Markdown artifact under .task/; what you capture — one task with its plan, an initiative with its architecture, or the decisions they must honor — is the skill name, never a flag. No execution skill: a session told implement .task/task/<slug>.md follows its ## Execution pointer, roadmap-to-workflow fans items out through the driver skills/_lib/roadmap-driver.js, and both hand the diff to the one agent, agents/code-reviewer.md. No build step, no plugin hook; the bash layer is tested and shellchecked in CI. Work here is mostly Markdown and pipeline reasoning.
discuss freely in chat
↓
grill ← pre-capture: interrogate the decision, no artifact
↓
to-task | to-roadmap ← what you capture is the skill, not a flag
to-spec ← pins technical decisions, cited via Spec:
↓ ↓
implement session roadmap-to-workflow ← the launcher fans items out to sessions
↓ ↓
task:code-reviewer ← the plugin's own review pass, spawned by both:
prove → fix within Touches → Build and Tests → commit the fixes
Verify
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 Changed · -29 tokens per session 72723955dbe5
- 1mo ago Changed · -1 lines · +37 tokens per session ef9a9ce0d6d4
- 1mo ago Changed · -7 lines · -2,262 tokens per session 27bc33ea7537
- 1mo ago Changed · +1 lines · +247 tokens per session 85e1de8d5ecd
- 1mo ago Changed · +3 lines · +610 tokens per session 04d3c29b6db3
- 1mo ago Changed · +19 tokens per session d7511b85f3ea
- 1mo ago Changed · +68 tokens per session 651f2213d61a
- 2mo ago First seen · 78 lines · 3,653 tokens per session scan A b37e6ceb9323
task-pipeline CLAUDE.md is an instructions file published in the GitHub repository SpaiR/task-pipeline (7 stars, last pushed 24d ago), licensed MIT. It adds 2,343 tokens to every session, about $0.0094 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.