Borrowing it
Nothing to install: this file belongs to will-pagane/claude-superdev-harness. 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/will-pagane/claude-superdev-harness/main/CLAUDE.mdgit clone --depth 1 https://github.com/will-pagane/claude-superdev-harnessWrote 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/will-pagane/claude-superdev-harness/claude-md)<a href="https://agentmods.dev/instructions/will-pagane/claude-superdev-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/will-pagane/claude-superdev-harness/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.01264 | $0.01264 |
| Opus 5 | $0.00632 | $0.00632 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
claude-superdev-harness 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 6d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Global CLAUDE.md — Mandatory Rules for All Projects
This file is law, not recommendation. Follow every rule exact.
Language
- Respond and comment code in Brazilian Portuguese, unless context need other language
- CLAUDE.md, code, memory files: always English
Naming Conventions
- Match existing project patterns first — codebase use
camelCasefor JSON keys → don't switch tosnake_case - Never mix conventions in same file/module
- Renaming → update all references across codebase, not just definition
Git branches & worktrees (per session)
Name every branch/worktree for what session doing + timestamp. NEVER keep tool auto-generated random name (e.g. claude/magical-jones-8c99, worktree-foo, perf-review) — rename or recreate to this scheme so concurrent sessions legible + sortable.
- Branch:
<type>/<task-slug>-<YYYYMMDD><type>= dominant work:feat|fix|refactor|perf|security|chore|docs|test|remediation|review.<task-slug>= 2–5 kebab-case words naming task (e.g.dup-correctness-remediation,anon-rpc-hardening).<YYYYMMDD>= date branch started; append-HHMMonly to break same-day collision.
- Worktree dir:
.claude/worktrees/<task-slug>-<YYYYMMDD>— mirror branch slug+timestamp (drop<type>/prefix; dir already isolated). Harness native worktree tool force own prefix (e.g.worktree-) → keep<task-slug>-<YYYYMMDD>core intact so stay descriptive + sortable. - Concurrency (mandatory): each concurrent session on same repo get own branch + worktree under this scheme — never share working dir across sessions, and verify
git branch --show-currentbefore any commit/push. - Cleanup: once merged, delete both branch and worktree (
git worktree remove <dir>+git branch -d <branch>). Branch fully reachable frommain= redundant — remove it. - Native worktree tool mangle branch name.
EnterWorktreewithchore/my-task-20260729produce branchworktree-chore+my-task-20260729. Rename immediately:git branch -m <type>/<task-slug>-<YYYYMMDD>, verify withgit branch --show-currentbefore first commit.
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.
- 6d ago First seen · 78 lines · 1,264 tokens per session scan A 1fe768eef5fb
claude-superdev-harness CLAUDE.md is an instructions file published in the GitHub repository will-pagane/claude-superdev-harness (4 stars, last pushed 4d ago), licensed MIT. It adds 1,264 tokens to every session, about $0.0063 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.
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.