Borrowing it
Nothing to install: this file belongs to felixgeelhaar/cclint. 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/felixgeelhaar/cclint/main/CLAUDE.mdgit clone --depth 1 https://github.com/felixgeelhaar/cclintWrote 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/felixgeelhaar/cclint/claude-md)<a href="https://agentmods.dev/instructions/felixgeelhaar/cclint/claude-md"><img src="https://agentmods.dev/badge/instructions/felixgeelhaar/cclint/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.01263 | $0.01263 |
| Opus 5 | $0.00632 | $0.00632 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
cclint 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is the CC Linter project - a TypeScript/Node.js tool designed to validate and optimize CLAUDE.md context files. The project follows a hexagonal architecture with a Core Linting Engine that is independent from its delivery mechanisms (CLI, IDE extensions).
Development Commands
# Development (uses tsx for fast execution)
npm test # Run tests with Vitest
npm run test:watch # Run tests in watch mode
# Production checks (uses tsc for strict type checking)
npm run typecheck # Type check with TypeScript compiler
npm run lint # Lint code
npm run build # Build for production
# Package management
npm ci # Install dependencies (CI)
npm install # Install dependencies
Architecture
The project uses a Domain-Driven Design approach with hexagonal architecture:
Core Domain Model
- ContextFile: In-memory representation of a file being linted
- Rule: Self-contained service that inspects a ContextFile and returns Violations
- Violation: Entity representing a broken rule with Location and Severity
- Location: Value object defining position of a Violation
- Severity: Value object (Error, Warning, Info)
- LintingResult: Root aggregate containing all Violations for a file
Architecture Layers
CLI (cclint) ──┐
MCP (cclint-mcp) ──┼──► Core Linting Engine (npm package)
LSP (cclint-lsp) ──┤ ├── Rules Engine (aggregates violations)
GitHub Action ──┘ ├── createRules(config) factory + rule descriptors
├── Individual Rules (implement Rule interface)
└── File System I/O (reads CLAUDE.md, config files)
All four entry points build their rule set from the single createRules(config)
factory (src/rules/registry/), driven by canonical RULE_DESCRIPTORS — one
source of truth for each rule's id, default-enabled flag, and metadata — so every
entry point runs an identical, in-lock-step rule set.
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 · 126 lines · 1,263 tokens per session scan A a5bc869b28e8
cclint CLAUDE.md is an instructions file published in the GitHub repository felixgeelhaar/cclint (11 stars, last pushed today), licensed MIT. It adds 1,263 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-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.
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.
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.