Borrowing it
Nothing to install: this file belongs to DenisSergeevitch/repo-task-proof-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/DenisSergeevitch/repo-task-proof-loop/main/CLAUDE.mdgit clone --depth 1 https://github.com/DenisSergeevitch/repo-task-proof-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/denissergeevitch/repo-task-proof-loop/claude-md)<a href="https://agentmods.dev/instructions/denissergeevitch/repo-task-proof-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/denissergeevitch/repo-task-proof-loop/claude-md.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.00424 | $0.00424 |
| Opus 5 | $0.00212 | $0.00212 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
repo-task-proof-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 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
Repo task proof loop
For substantial features, refactors, and bug fixes, use the repo-task-proof-loop workflow.
Required artifact path:
- Keep all task artifacts in
.agent/tasks/<TASK_ID>/inside this repository.
Required sequence:
- Freeze
.agent/tasks/<TASK_ID>/spec.mdbefore implementation. - Implement against explicit acceptance criteria (
AC1,AC2, ...). - Create
evidence.md,evidence.json, and raw artifacts. - Run a fresh verification pass against the current codebase and rerun checks.
- If verification is not
PASS, writeproblems.md, apply the smallest safe fix, and reverify.
Hard rules:
- Do not claim completion unless every acceptance criterion is
PASS. - Verifiers judge current code and current command results, not prior chat claims.
- Fixers should make the smallest defensible diff.
Installed workflow agents:
.claude/agents/task-spec-freezer.md.claude/agents/task-builder.md.claude/agents/task-verifier.md.claude/agents/task-fixer.md
Claude Code note:
- If
initjust created or refreshed these files during the current Claude Code session, do not assume the refreshed workflow agents are already available. - The main Claude session may auto-delegate to these workflow agents when the current proof-loop phase matches their descriptions. If automatic delegation is not precise enough, make the current proof-loop phase more explicit in natural language.
- TodoWrite or the visible task/todo UI is optional session-scoped progress display only. The canonical durable proof-loop state is the repo-local artifact set under
.agent/tasks/<TASK_ID>/. - Keep this workflow flat. These generated workflow agents are role endpoints, not recursive orchestrators.
- Keep this block in the root
CLAUDE.md. If the workflow needs longer repo guidance, prefer@pathimports or.claude/rules/*.mdinstead of expanding this block.
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 · 34 lines · 424 tokens per session scan A 5ef474c55512
repo-task-proof-loop CLAUDE.md is an instructions file published in the GitHub repository DenisSergeevitch/repo-task-proof-loop (729 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 424 tokens to every session, about $0.0021 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-30.
Other instructions, from other repositories
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).
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.
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 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).
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.