quench: Instructions file for Claude Code

CLAUDE.md

quench CLAUDE.md is an instructions file for Claude Code from alfredjeanlab/quench. It costs 522 tokens per session, scanned A, original, MIT.

Repository instructions for Quench, a Rust quality-benchmarking and linting tool. They describe its folders, separate Rust test files, development process, and commit practices.

In plain words
What is it for?
Use them when changing Quench, especially when adding Rust code, writing tests, updating specifications or plans, or preparing commits.
Why use it?
They give an agent the project-specific rules needed to place code and tests correctly and follow the repository’s development process.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is alfredjeanlab/quench's own configuration. It tells Claude Code how to work on quench itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything quench configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alfredjeanlab/quench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alfredjeanlab/quench/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/alfredjeanlab/quench

Made for: Claude Code.

Wrote 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.

agentmods badge for quench CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alfredjeanlab/quench/claude-md/github.svg)](https://agentmods.dev/instructions/alfredjeanlab/quench/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/alfredjeanlab/quench/claude-md"><img src="https://agentmods.dev/badge/instructions/alfredjeanlab/quench/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.

agentmods 80×15 button for quench CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alfredjeanlab/quench/claude-md"><img src="https://agentmods.dev/badge/instructions/alfredjeanlab/quench/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 522 This file is loaded in full into every session.
When invoked 522 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00522 $0.00522
Opus 5.5 $0.00209 $0.00209
Sonnet 5.5 $0.00104 $0.00104
Haiku 4.5 $0.00052 $0.00052

Measured 2mo ago against content hash df791112fdfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quench 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 2mo 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.

CLAUDE.md · 74 lines

What it actually says

Quench (Quality Benchmarks)

A fast linting tool for AI agents that measures quality signals. Configured via quench.toml.

Directory Structure

quench/
├── README.md         # Human-focused introduction
├── crates/           # Rust workspace
│   └── cli/          # CLI binary
├── docs/
│   ├── specs/        # Feature specifications (the "what")
│   └── arch/         # Architecture decisions
├── plans/            # Implementation plans (the "how" and "when")
├── tests/
│   ├── specs/        # Behavioral tests (black-box, see tests/specs/CLAUDE.md)
│   └── fixtures/     # Test projects
└── scripts/          # Build and utility scripts

Unit Test Convention

Use sibling _tests.rs files instead of inline #[cfg(test)] modules:

// src/parser.rs
#[cfg(test)]
#[path = "parser_tests.rs"]
mod tests;
// src/parser_tests.rs
#![allow(clippy::unwrap_used, clippy::expect_used, clippy::panic)]
use super::*;

#[test]
fn parses_empty_input() { ... }

Why separate files?

  • Shorter source files fit better in LLM context windows
  • LOC metrics reflect implementation conciseness, not test volume
  • Integration tests remain in tests/ as usual

Development Lifecycle

  1. Specs are written from docs/specs/, not from implementation
  2. Write specs first, mark unimplemented with #[ignore = "TODO: Phase N"]
  3. Implement feature in src/
  4. Remove #[ignore], verify specs pass
  5. List passing specs in commit message

Commits

Use conventional commit format: type(scope): description

Types: feat, fix, chore, docs, test, refactor, perf, ci, build, style

Landing the Plane

Before committing changes:

  • Unit tests in sibling _tests.rs files
  • Bump CACHE_VERSION in crates/cli/src/cache.rs if check logic changed
  • Run make check which will
    • cargo fmt --all
    • cargo clippy --all -- -D warnings
    • cargo build --all
    • cargo test --all
    • cargo run -- check
Changes

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.

  1. 2mo ago First seen · 74 lines · 522 tokens per session scan A df791112fdfc

Subscribe to this mod's changes

quench CLAUDE.md is an instructions file published in the GitHub repository alfredjeanlab/quench (2 stars, last pushed 6mo ago), licensed MIT. It adds 522 tokens to every session, about $0.0021 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-31.

Related

quench CLAUDE.md compared with instructions from other repositories

quench CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
quench CLAUDE.mdalfredjeanlab/quenchInstructions file26mo agoMITA522Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file144ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file150ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,086GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file282k3d agoMITA4,335Codex, OpenCode