Borrowing it
Nothing to install: this file belongs to Vvlladd/qrspi-orchestrator. 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/Vvlladd/qrspi-orchestrator/main/CLAUDE.mdgit clone --depth 1 https://github.com/Vvlladd/qrspi-orchestratorWrote 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/vvlladd/qrspi-orchestrator/claude-md)<a href="https://agentmods.dev/instructions/vvlladd/qrspi-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/vvlladd/qrspi-orchestrator/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/vvlladd/qrspi-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/vvlladd/qrspi-orchestrator/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.01908 | $0.01908 |
| Opus 5 | $0.00954 | $0.00954 |
| Sonnet 5 | $0.00382 | $0.00382 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
qrspi-orchestrator 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QRSPI Pipeline
Multi-agent orchestration for feature development with human-in-the-loop checkpoints.
Pipeline Phases
Execute phases in order. STOP after each phase and wait for human approval before proceeding. Never auto-proceed.
Phase 1: Questions
- Read the feature request
- Scan the codebase for relevant patterns, files, and conventions (max 10 file reads)
- Identify ambiguities, edge cases, unstated assumptions
- Write
reports/01-requirements.mdwith: Summary, Acceptance Criteria (specific, testable), Edge Cases, Out of Scope, Open Questions, Existing Code Context - Present summary and ask: "Approve, request changes, or reject?"
Phase 2: Research
Explore the codebase in depth:
- Map all relevant files (models, protocols, engines, configs, tests)
- Analyze existing patterns and conventions
- Identify dependencies (internal modules, external packages, APIs)
- Assess risks and complexity
- Write
reports/02-exploration.mdwith: File Map, Existing Patterns, Dependencies, Architecture Notes, Risks, Suggested Approach - Cite file paths and line numbers for every claim
- Present summary and ask for approval
Phase 3: Design
Produce a clear, actionable design:
- Read requirements and exploration report
- Design component boundaries, interfaces, data flow
- Define test strategy per component
- Write
reports/03-design.mdwith: Overview, Components (files, responsibility, interface, dependencies), Data Flow, Interface Contracts, Error Handling, Test Strategy, Migration/Breaking Changes
Then challenge your own design:
- Is this the simplest approach? What's simpler?
- What happens at scale, under load, with concurrent users?
- What are the failure modes?
- Are interfaces over-engineered or under-specified?
- Any security concerns? (auth, injection, data exposure, input validation)
Revise the design based on self-critique. Present summary and ask for approval.
Phase 4: Plan
Decompose the design into ordered tasks:
- Each task: 2-5 minutes of implementation work
- One concern per task (don't mix implementation with tests)
- Tests are separate tasks
- Include setup tasks (packages, migrations, configs)
- Final task is always integration verification
- Write
tasks.jsonwith: id, title, description, files, acceptance_criteria, depends_on, estimated_minutes, status - Write
reports/04-plan.mdwith human-readable table - Present task breakdown and ask for approval (human can reorder, split, merge, remove)
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 · 155 lines · 1,908 tokens per session scan A 85154f4e7d1a
qrspi-orchestrator CLAUDE.md is an instructions file published in the GitHub repository Vvlladd/qrspi-orchestrator (6 stars, last pushed 9d ago), licensed MIT. It adds 1,908 tokens to every session, about $0.0095 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.