Borrowing it
Nothing to install: this file belongs to heyhank-app/heyhank. 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/heyhank-app/heyhank/main/CLAUDE.mdgit clone --depth 1 https://github.com/heyhank-app/heyhankWrote 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/heyhank-app/heyhank/claude-md)<a href="https://agentmods.dev/instructions/heyhank-app/heyhank/claude-md"><img src="https://agentmods.dev/badge/instructions/heyhank-app/heyhank/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.02566 | $0.02566 |
| Opus 5 | $0.01283 | $0.01283 |
| Sonnet 5 | $0.00513 | $0.00513 |
| Haiku 4.5 | $0.00257 | $0.00257 |
Grade A, and why
heyhank CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `./scripts/dev-start.sh` health-checks the backend on `/` which returns 404. If the script times out, the backend is still running — verify with `curl http://localhost:3457/api/sessions`. You can start the servers manu How it starts
The opening of the file, as written. The whole thing — 202 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 & Codex when working with code in this repository.
What This Is
The Companion — a web UI for Claude Code & Codex.
It reverse-engineers the undocumented --sdk-url WebSocket protocol in the Claude Code CLI to provide a browser-based interface for running multiple Claude Code sessions with streaming, tool call visibility, and permission control.
Development Commands
# Dev server (Hono backend on :3456 + Vite HMR on :5174)
cd web && bun install && bun run dev
# Or from repo root
make dev
# Type checking
cd web && bun run typecheck
# Production build + serve
cd web && bun run build && bun run start
# Auth token management
cd web && bun run generate-token # show current token
cd web && bun run generate-token --force # regenerate a new token
# Landing page (thecompanion.sh) — idempotent: starts if down, no-op if up
# IMPORTANT: Always use this script to run the landing page. Never cd into landing/ and run bun/vite manually.
./scripts/landing-start.sh # start
./scripts/landing-start.sh --stop # stop
Testing
# Run tests
cd web && bun run test
# Watch mode
cd web && bun run test:watch
- All new backend (
web/server/) and frontend (web/src/) code must include tests when possible. - Every new or modified frontend component (
web/src/components/) must have an accompanying.test.tsxfile with at minimum: a render test, an axe accessibility scan (toHaveNoViolations()), and tests for any interactive behavior (clicks, keyboard shortcuts, state changes). - Tests use Vitest. Server tests live alongside source files (e.g.
routes.test.tsnext toroutes.ts). - A husky pre-commit hook runs typecheck and tests automatically before each commit.
- Never remove or delete existing tests. If a test is failing, fix the code or the test. If you believe a test should be removed, you must first explain to the user why and get explicit approval before removing it.
- When creating test, make sure to document what the test is validating, and any important context or edge cases in comments within the test code.
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 · 202 lines · 2,566 tokens per session scan A fb2531b52396
heyhank CLAUDE.md is an instructions file published in the GitHub repository heyhank-app/heyhank (34 stars, last pushed 3mo ago), licensed MIT. It adds 2,566 tokens to every session, about $0.0128 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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).
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.