ccstatus-go: Instructions file for Claude Code

CLAUDE.md

ccstatus-go CLAUDE.md is an instructions file for Claude Code from Mirage20/ccstatus-go. It costs 1,030 tokens per session, scanned A, original, MIT.

Repository instructions for ccstatus-go, a Go program that generates a status line for Claude Code.

In plain words
What is it for?
Use them when building, linting, testing, or changing providers and components in the ccstatus-go repository.
Why use it?
They give coding agents the project's commands, architecture, and conventions so changes fit the existing codebase.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is Mirage20/ccstatus-go's own configuration. It tells Claude Code how to work on ccstatus-go itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ccstatus-go configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Mirage20/ccstatus-go/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Mirage20/ccstatus-go

Made for: Claude Code.

Wrote 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.

agentmods badge for ccstatus-go CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mirage20/ccstatus-go/claude-md.svg)](https://agentmods.dev/instructions/mirage20/ccstatus-go/claude-md)
Your own site
<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>
Per session 1,030 This file is loaded in full into every session.
When invoked 1,030 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash 12d2294502eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

CLAUDE.md · 125 lines

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

  1. Providers (internal/providers/) - Fetch data from various sources

    • Each provider implements Provider interface with Key() and Provide(ctx) methods
    • Self-register via init() functions when imported
    • Providers run in parallel during data gathering via goroutines
    • Wrapped with CachingProvider for TTL-based caching
  2. Components (internal/components/) - Render specific parts of the status line

    • Each component implements Component interface with Render(ctx) and RequiredProviders() methods
    • Self-register via init() functions with name string when imported
    • Component order determined by config or defaults
    • Optional OptionalComponent interface for conditional rendering
  3. 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

  1. Main reads Claude session JSON from stdin
  2. Load configuration via Koanf
  3. Create cache (FileCache or NullCache based on config)
  4. Determine active components from config
  5. Create only required providers based on component dependencies
  6. StatusLine.Render() executes providers in parallel, then renders components
  7. Output printed to stdout with ANSI colors

Read the full file on GitHub · 125 lines

Changes

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.

  1. 7d ago First seen · 125 lines · 1,030 tokens per session scan A 12d2294502eb

Subscribe to this mod's changes

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.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens