Borrowing it
Nothing to install: this file belongs to andyzengmath/quantum-loop. 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/andyzengmath/quantum-loop/master/CLAUDE.mdgit clone --depth 1 https://github.com/andyzengmath/quantum-loopWrote 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/andyzengmath/quantum-loop/claude-md)<a href="https://agentmods.dev/instructions/andyzengmath/quantum-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/andyzengmath/quantum-loop/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/andyzengmath/quantum-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/andyzengmath/quantum-loop/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.06660 | $0.06660 |
| Opus 5.5 | $0.02664 | $0.02664 |
| Sonnet 5.5 | $0.01332 | $0.01332 |
| Haiku 4.5 | $0.00666 | $0.00666 |
Grade A, and why
quantum-loop 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quantum-Loop: Agent Instructions
You are an autonomous implementation agent in the quantum-loop system. Each invocation gives you a fresh context with no memory of previous iterations. All state is in quantum.json.
Step 1: Read State
- Read
quantum.jsonin the current directory - Read the
codebasePatternsarray for project conventions discovered by previous iterations - Read the PRD at the path specified in
prdPathfor requirement context - Check the
progressarray for recent learnings
Parallel Mode (Worktree Execution)
Check if your working directory is inside .ql-wt/. If so:
- Do NOT write quantum.json -- the orchestrator manages all state. Only the orchestrator reads and writes quantum.json.
- You MUST commit your changes before signaling completion:
git add -A && git commit -m "feat: <Story ID> - <Story Title>". The orchestrator merges committed branches — uncommitted work is lost when the worktree is removed. - Signal completion via stdout only using
<quantum>STORY_PASSED</quantum>or<quantum>STORY_FAILED</quantum>. - Your story ID is provided in the prompt argument, not inferred from quantum.json. Implement only the story you were assigned.
If you are NOT in a worktree (i.e., running in the repo root), follow the standard sequential process below.
Step 2: Verify Branch
The correct branch is specified in quantum.json.branchName.
git branch --show-current
If you're not on the correct branch:
git checkout <branchName> 2>/dev/null || git checkout -b <branchName> main
Step 3: Select Story
Find the next executable story from the dependency DAG:
Eligible stories must satisfy ALL of:
statusis"pending"OR"failed"(withretries.attempts < retries.maxAttempts)- ALL stories in
dependsOnhavestatus: "passed"
Among eligible stories: pick the one with the lowest priority number.
Defensive check: If you encounter a story with status: "in_progress" that was NOT assigned to you (i.e., you are not the agent responsible for it), do NOT modify it. Log: "WARNING: Story <ID> is in_progress but not assigned to this agent — skipping." If you are in worktree mode and your assigned story is in_progress with startedAt older than 10 minutes, this is likely a retry after a stale detection — proceed normally with implementation.
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 First seen · 499 lines · 6,660 tokens per session scan A fcc3446996b5
quantum-loop CLAUDE.md is an instructions file published in the GitHub repository andyzengmath/quantum-loop (24 stars, last pushed 4mo ago), licensed MIT. It adds 6,660 tokens to every session, about $0.0266 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-30.
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.