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/cnighswonger/claude-code-meter/claude-mdgit clone --depth 1 https://github.com/cnighswonger/claude-code-meterWrote 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/cnighswonger/claude-code-meter/claude-md)<a href="https://agentmods.dev/instructions/cnighswonger/claude-code-meter/claude-md"><img src="https://agentmods.dev/badge/instructions/cnighswonger/claude-code-meter/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.01990 | $0.01990 |
| Opus 5 | $0.00995 | $0.00995 |
| Sonnet 5 | $0.00398 | $0.00398 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
claude-code-meter 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: claude-meter
Session State
On resume, compaction, or context loss: Read SESSION_STATE.md in this directory immediately. It contains the current working state — infrastructure, pending tasks, recent fixes, and architectural constraints. Update it when significant state changes occur.
Never post publicly without Chris's approval. Draft and wait for go-ahead.
Overview
Community usage metrics collector for Claude Code. Captures anonymized billing data from API responses to enable statistical analysis of Anthropic's pricing model through community data aggregation.
Git Workflow
- Do not push directly to
mainunless the user explicitly instructs you to do so in the current turn. Otherwise use feature branches and PRs, even for small fixes. - If writing directly to
mainis explicitly authorized, pull/rebase fromorigin/mainbefore any other write action so you start from the current remote tip. - Branch naming:
feature/<name>for features,fix/<name>for bugfixes. - Commit messages: lead with what changed and why, not how.
Repository Structure
bin/claude-meter.mjs— CLI entry point (status, history, rates, share, setup)src/constants.mjs— paths, known API rates, rate-limit header namesinterceptor/— Node.js fetch interceptor (loaded viaNODE_OPTIONS=--import)preload.mjs— entry point for--importfetch-patch.mjs—response.clone()based fetch wrapperusage-extractor.mjs— drains cloned SSE stream for usage objectintegrity.mjs— self-hash tamper detection on load
log/— local JSONL data layerschema.mjs— Zod schemas (per-turn row + community share payload)writer.mjs— build and append validated JSONL rowsreader.mjs— parse, filter, group JSONL for CLI
cli/— CLI command implementationsstatus.mjs— current session summaryhistory.mjs— daily/weekly usage aggregatesrates.mjs— OLS regression for billing weight estimationshare.mjs— interactive payload review + community submissionsetup.mjs— wrapper detection and interceptor integration
share/— community data pipelinepayload-builder.mjs— aggregates per-turn JSONL into per-session share payloadclient.mjs— HTTP client for community API endpoint
server/index.mjs— community API server (deployed separately)
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.
- 5d ago First seen · 113 lines · 1,990 tokens per session scan A 628286472c71
claude-code-meter CLAUDE.md is an instructions file published in the GitHub repository cnighswonger/claude-code-meter (2 stars, last pushed 29d ago), licensed MIT. It adds 1,990 tokens to every session, about $0.0100 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
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).
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.
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).