Borrowing it
Nothing to install: this file belongs to mkalkere/claude-statusline. 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/mkalkere/claude-statusline/main/CLAUDE.mdgit clone --depth 1 https://github.com/mkalkere/claude-statuslineWrote 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/mkalkere/claude-statusline/claude-md)<a href="https://agentmods.dev/instructions/mkalkere/claude-statusline/claude-md"><img src="https://agentmods.dev/badge/instructions/mkalkere/claude-statusline/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/mkalkere/claude-statusline/claude-md"><img src="https://agentmods.dev/badge/instructions/mkalkere/claude-statusline/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00679 | $0.00679 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
claude-statusline 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 10d 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.
Project Rules — claude-statusline
Non-negotiable rules
-
NEVER add AI attribution — No "Co-Authored-By", "Generated with", "Written by", or any reference to Claude, Gemini, or any AI tool in commits, PRs, release notes, documentation, or any output. Zero exceptions.
-
No secrets or credentials — Never commit API keys, tokens, passwords, paths with real usernames, or any sensitive data. All paths in code/tests must use generic placeholders like
/home/user/projects/myapp. -
Zero external dependencies — Pure Python stdlib only. No pip packages. This is a core selling point of the project. Never add dependencies without explicit approval.
-
No references to other projects — Don't mention competitor tools, internal projects, company names, or other repos in code, commits, or docs.
-
High code quality — This is a public open-source project on PyPI. Every change is visible to the community. Code must be production-grade.
Development practices
- Always run the full test suite before committing
- Always run the PR review plugin (all 4 agents: code-reviewer, test-analyzer, silent-failure-hunter, comment-analyzer) and iterate until zero issues
- Check Gemini PR comments and address them
- Keep CHANGELOG.md up to date with every version
- Update README feature tables and examples when adding features
- Bump version in both
__init__.pyandpyproject.toml - After merge, create a GitHub release to trigger PyPI publish
- Close related GitHub issues after release
- Install from PyPI and verify the release works
For the step-by-step release runbook (review-cycle pattern, agent briefing, post-merge sequence, failure-mode catalog), see docs/RELEASE.md.
Code patterns
- Use
_first()helper for numeric fields (notorwhich drops zeros) - Use
_safe_num()for coercing external numeric values - Use
isinstance()checks before.get()on external JSON data - All section renderers must degrade gracefully — never crash
render()call inmain()is wrapped in try/except as defense-in-depth- Cache reads use TTL-based file caching in user-scoped temp directories
- Cache writes use atomic
os.replace()pattern - Git operations use 5s cache TTL, "not available" state uses 60s TTL
- Tool count uses 10s TTL, other session data uses 30s TTL
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.
- 10d ago First seen · 55 lines · 679 tokens per session scan A c192f3438a31
claude-statusline CLAUDE.md is an instructions file published in the GitHub repository mkalkere/claude-statusline (3 stars, last pushed 17d ago), licensed MIT. It adds 679 tokens to every session, about $0.0034 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
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.
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.
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).
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.