Borrowing it
Nothing to install: this file belongs to Mirage20/ccstatus-go. 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/Mirage20/ccstatus-go/main/CLAUDE.mdgit clone --depth 1 https://github.com/Mirage20/ccstatus-goWrote 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/mirage20/ccstatus-go/claude-md)<a href="https://agentmods.dev/instructions/mirage20/ccstatus-go/claude-md"><img src="https://agentmods.dev/badge/instructions/mirage20/ccstatus-go/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.01030 | $0.01030 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
ccstatus-go 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 7d 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 — 125 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.
Commands
Build
make build # Build to build/ccstatus with optimizations (-s -w flags)
make all # Run lint and build
make clean # Clean build artifacts
Lint
make lint # Run golangci-lint with strict .golangci.yaml config
make lint-fix # Auto-fix linting issues
Test
make test # Run tests
Architecture
This is a Go implementation of a Claude Code statusline generator that follows a provider-component architecture with self-registering plugins.
Core Pattern
-
Providers (
internal/providers/) - Fetch data from various sources- Each provider implements
Providerinterface withKey()andProvide(ctx)methods - Self-register via init() functions when imported
- Providers run in parallel during data gathering via goroutines
- Wrapped with
CachingProviderfor TTL-based caching
- Each provider implements
-
Components (
internal/components/) - Render specific parts of the status line- Each component implements
Componentinterface withRender(ctx)andRequiredProviders()methods - Self-register via init() functions with name string when imported
- Component order determined by config or defaults
- Optional
OptionalComponentinterface for conditional rendering
- Each component implements
-
StatusLine (
internal/core/statusline.go) - Main orchestrator- Gathers data from all providers in parallel
- Renders components in configured order
- Handles separator formatting between components
Data Flow
- Main reads Claude session JSON from stdin
- Load configuration via Koanf
- Create cache (FileCache or NullCache based on config)
- Determine active components from config
- Create only required providers based on component dependencies
- StatusLine.Render() executes providers in parallel, then renders components
- Output printed to stdout with ANSI colors
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.
- 7d ago First seen · 125 lines · 1,030 tokens per session scan A 12d2294502eb
ccstatus-go CLAUDE.md is an instructions file published in the GitHub repository Mirage20/ccstatus-go (11 stars, last pushed 2mo ago), licensed MIT. It adds 1,030 tokens to every session, about $0.0052 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.
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.