Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/codingbutter/code-health/claude-mdgit clone --depth 1 https://github.com/CodingButter/code-healthWhat 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 | $0.01325 | $0.01325 |
| Opus 5 | $0.00662 | $0.00662 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
code-health 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 2d 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 — 152 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 repository will contain @butter/code-health, a global Node.js CLI tool for analyzing code health in TypeScript/JavaScript projects. The tool provides static analysis, dependency visualization, and code quality metrics through a browser-based dashboard.
Architecture
Core Components
-
CLI Entry Point (
src/index.ts)- Commands:
analyze,dashboard,print - Uses commander or sade for CLI parsing
- Global installation via
npm i -gor runnable withnpx
- Commands:
-
Analysis Runners (
src/core/runners/)- ESLint runner with TypeScript, SonarJS, Unicorn, and Regexp plugins
- Dependency-cruiser for dependency graph analysis
- Knip for dead code detection
- Cloc for line counting
-
Dashboard Server (
src/server/)- Fastify-based API server
- WebSocket support for live updates
- Serves Vite-built React UI from
dist/ui
-
React UI (
ui/)- Vite + React single-page application
- Tables for: largest files, complexity metrics, dependency cycles, dead code, max-lines violations
- Auto-refresh via WebSocket in watch mode
Key Implementation Patterns
- Zero repo churn: All reports written to temp directories (
~/.butter-code-health/<hash>/.reports/or OS temp) - Monorepo-aware: Detects workspaces via package.json, pnpm-workspace.yaml
- Config resolution: Respects existing ESLint/TypeScript configs, falls back to internal defaults
- Unified ignore strategy: Combines .gitignore with built-in patterns (node_modules, dist, build, etc.)
Development Commands
# Initial setup (once codebase exists)
pnpm install
# Build the CLI and UI
pnpm build # Build both CLI (to dist/cli.cjs) and UI (to dist/ui)
pnpm build:cli # Build CLI only
pnpm build:ui # Build UI only
# Development
pnpm dev # Run CLI in watch mode
pnpm dev:ui # Run Vite dev server for UI
# Testing
pnpm test # Run tests
pnpm test:watch # Run tests in watch mode
# Linting & Type Checking
pnpm lint # Run ESLint
pnpm typecheck # Run TypeScript type checking
# Local testing of the CLI
pnpm link # Link package globally for testing
npx @butter/code-health analyze # Test analyze command
npx @butter/code-health dashboard # Test dashboard command
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.
- 2d ago First seen · 152 lines · 1,325 tokens per session scan A e6ce8865ba62
code-health CLAUDE.md is an instructions file published in the GitHub repository CodingButter/code-health (3 stars, last pushed 1y ago), licensed MIT. It adds 1,325 tokens to every session, about $0.0066 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
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.
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).
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.