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/backstabslash/goccc/claude-mdgit clone --depth 1 https://github.com/backstabslash/gocccWrote 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/backstabslash/goccc/claude-md)<a href="https://agentmods.dev/instructions/backstabslash/goccc/claude-md"><img src="https://agentmods.dev/badge/instructions/backstabslash/goccc/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 | $0.00984 | $0.00984 |
| Opus 5 | $0.00492 | $0.00492 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
goccc 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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goccc
CLI tool that parses Claude Code JSONL logs from ~/.claude/projects/ and calculates API usage costs by model, day, project, and branch.
Stack
Go 1.26, stdlib only (zero external deps), GoReleaser for cross-platform builds
Commands
go build -o goccc . # Build binary
go test ./... # Run all tests
go vet ./... # Static analysis
go run . -days 7 -all # Dev: run with flags directly
Verification
Run before every commit:
make check
JSONL Log Format
Claude Code stores logs at ~/.claude/projects/<project-slug>/. Sessions are <uuid>.jsonl with subagents in <uuid>/subagents/agent-<id>.jsonl. Workflow-spawned agents nest deeper, under <uuid>/subagents/workflows/wf_*/agent-<id>.jsonl.
- Only
type: "assistant"entries carrymessage.modelandmessage.usage— skip all others output_tokensalready includes thinking tokens — no separate countercache_creationsub-object breaks down 5m/1h tiers;cache_creation_input_tokensis the flat total (fallback for older logs)- One API call produces multiple entries sharing the same
requestId— dedup by keeping the last (highestoutput_tokens) model: "<synthetic>"+isApiErrorMessage: trueare rate-limit placeholders — filter out to avoid inflating counts
Conventions
- Flat package — all code in
package main, one concern per file - Externalized pricing — all pricing lives in
pricing.json(embedded via//go:embed, remote-cached 24h). Adding a model or adjusting pricing = editpricing.jsononly, no code changes. Cache fields are optional —fillCacheDefaults()derives from input price. Fast mode pricing lives infast_modelsmap — same structure asmodels, resolved whenusage.speed == "fast" - Pricing resolution — exact model ID → longest family prefix →
defaultPricing - Time-based pricing — a model's base price applies from the beginning of time; an optional
schedule: [{ "from": "YYYY-MM-DD", ...prices }]adds dated overrides, and cost uses the entry with the greatestfrom≤ the message timestamp. An entry is a diff over the base: omitted primaries (input/output, long-ctx) inherit the base — so a base bump keeps the long-context tier — but omitted cache tiers re-derive from the entry's own input, not the base's cache.fromis midnight UTC, a billing boundary independent of the-utcdisplay flag - Fast mode bucketing — parser appends
:fastsuffix to model key whenspeed == "fast", creating separate buckets.shortModel()andresolvePricing()strip the suffix for display/lookup - Local timezone everywhere — day bucketing/cutoffs use
parseLocation(defaults totime.Local). NeverUTC()for user-facing dates. The-utcflag is the one sanctioned opt-in: it setsparseLocation = time.UTCto match Anthropic API reporting - MCP detection is best-effort — returns nil/empty on error; statusline never fails due to missing config
- Config —
~/.goccc.jsonstores currency, thresholds, and statusline config.initConfig()loads once. JSON output costs always in USD - Session end hook — writes to
/dev/tty(bypasses Claude Code's stderr capture), falls back to stderr on Windows. Silently exits on any error - Statusline segments — registry in
statusline_config.go. Segments with no data auto-hide."|"forces line break
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.
- 4d ago First seen · 55 lines · 984 tokens per session scan A ff30468a1980
goccc CLAUDE.md is an instructions file published in the GitHub repository backstabslash/goccc (34 stars, last pushed 23d ago), licensed MIT. It adds 984 tokens to every session, about $0.0049 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
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.
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.
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.