Borrowing it
Nothing to install: this file belongs to SeongwoongCho/adaptive-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/SeongwoongCho/adaptive-harness/main/CLAUDE.mdgit clone --depth 1 https://github.com/SeongwoongCho/adaptive-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/seongwoongcho/adaptive-harness/claude-md)<a href="https://agentmods.dev/instructions/seongwoongcho/adaptive-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/seongwoongcho/adaptive-harness/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/seongwoongcho/adaptive-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/seongwoongcho/adaptive-harness/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.00857 | $0.00857 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
adaptive-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 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adaptive-harness — Project Instructions for AI Agents
Git Workflow
This project follows a structured branching strategy. All AI agents must follow these rules without exception.
Branch Structure
| Branch | Purpose |
|---|---|
main |
Stable releases only. Contains tagged versions. |
dev |
Integration branch. All feature work is merged here first. |
feat/*, fix/*, docs/*, harness/*, fixture/*, chore/* |
Short-lived feature branches. Always branched from dev. |
Rules for AI Agents
- Never commit directly to
mainordev. - Always create a new feature branch from
devbefore making any changes.git checkout dev git pull origin dev git checkout -b feat/<short-description> - All pull requests must target
dev, notmain. - Branch naming convention: Use one of the following prefixes:
feat/— new feature or capabilityfix/— bug fixdocs/— documentation onlyharness/— harness definition changesfixture/— fixture or test data changeschore/— maintenance, version bumps, tooling
Release Flow
Automated Release (recommended)
Use the prepare-release workflow to automate version bumping and PR creation:
- Go to Actions → Prepare Release → Run workflow on GitHub.
- Enter the new version (e.g.
1.2.0) and click Run workflow. - The workflow will:
- Run
scripts/bump_version.py <version>to update all version files. - Commit the version bump to
dev. - Open a PR from
dev→mainwith auto-generated release notes.
- Run
- Review and merge the PR.
- Tag the merge commit:
git tag v1.2.0 && git push origin v1.2.0. - The release workflow runs automatically on tag push, validates the version, generates the changelog, and creates a GitHub Release.
Manual Release
When a version is ready to release manually:
- Bump all version files in one command:
python3 scripts/bump_version.py <new_version> - Commit, push, and open a PR from
dev→main. - Merge the PR, then tag the merge commit on
main:git tag v<new_version> git push origin v<new_version>
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 · 88 lines · 857 tokens per session scan A 61c15a88e57b
adaptive-harness CLAUDE.md is an instructions file published in the GitHub repository SeongwoongCho/adaptive-harness (8 stars, last pushed 5mo ago), licensed MIT. It adds 857 tokens to every session, about $0.0043 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.