ccs: Instructions file for Claude Code

CLAUDE.md

ccs CLAUDE.md is an instructions file for Claude Code from yusufalikync/ccs. It costs 2,296 tokens per session, scanned B, original, MIT.

A Node.js package that installs a Claude Code status display showing usage percentages, session information, weekly usage, and cost. Node.js is software for running JavaScript outside a web browser.

In plain words
What is it for?
Use it to install, remove, or inspect the status display, test its output with sample data, run smoke tests, and check a package before publishing it to npm.
Why use it?
It makes resource and spending information visible while Claude Code is being used.

Instructions file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions Claude Code.

This is yusufalikync/ccs's own configuration. It tells Claude Code how to work on ccs 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 ccs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yusufalikync/ccs. 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/yusufalikync/ccs/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/yusufalikync/ccs

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 ccs CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yusufalikync/ccs/claude-md/github.svg)](https://agentmods.dev/instructions/yusufalikync/ccs/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/yusufalikync/ccs/claude-md"><img src="https://agentmods.dev/badge/instructions/yusufalikync/ccs/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.

agentmods 80×15 button for ccs CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yusufalikync/ccs/claude-md"><img src="https://agentmods.dev/badge/instructions/yusufalikync/ccs/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,296 This file is loaded in full into every session.
When invoked 2,296 The same file — it is already loaded in full.
Security scan B 2 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.02296 $0.02296
Opus 5.5 $0.00918 $0.00918
Sonnet 5.5 $0.00459 $0.00459
Haiku 4.5 $0.00230 $0.00230

Measured 2mo ago against content hash df984e6c3036, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

ccs CLAUDE.md scanned grade B with 2 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 2mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

**Install**: `src/check-deps.js` (verifies Node >= 18) → copies `scripts/statusline.js` to `~/.claude/statusline.js` → cleans up old `statusline.sh` if present → `settings.js` merges `statusLine` key into `~/.claude/sett

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Zero dependencies** — only Node.js built-ins (fs, os, path, child_process, url)
CLAUDE.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ccs-stats (ccs)

npm package that installs a Node.js statusline script into ~/.claude/ and configures settings.json to display real-time usage stats (context %, session %, weekly %, cost). The npm layer is the installer — the actual work happens in scripts/statusline.js.

Commands

# Test CLI locally
node bin/cli.js install
node bin/cli.js uninstall
node bin/cli.js status

# Test statusline.js directly with mock input
echo '{"model":{"display_name":"Opus 4"},"cost":{"total_cost_usd":0.5},"context_window":{"used_percentage":42},"workspace":{"current_dir":"/tmp/test"},"session_id":"dev"}' | node scripts/statusline.js

# Run smoke tests
npm test

# Dry-run npm publish check
npm pack --dry-run

# Publish to npm (runs npm test via prepublishOnly hook)
npm publish

# Release with full checklist (clean state, test, tag, publish)
bash scripts/release.sh

There are no build steps and no linter configured. Smoke tests run via npm test (14 tests in scripts/smoke-test.js). prepublishOnly runs tests automatically before npm publish.

Architecture

  • ES Modules ("type": "module") — all .js files use import/export
  • Zero dependencies — only Node.js built-ins (fs, os, path, child_process, url)
  • Cross-platform — macOS and Linux (verified); Windows experimental (credential access unverified)

Flow

bin/cli.js parses argv → dynamic-imports src/install.js, src/uninstall.js, or src/status.js.

Install: src/check-deps.js (verifies Node >= 18) → copies scripts/statusline.js to ~/.claude/statusline.js → cleans up old statusline.sh if present → settings.js merges statusLine key into ~/.claude/settings.json (with timestamped backup).

Test: scripts/smoke-test.js — runs statusline with 11 mock inputs (normal, null, empty, high, overflow, zero + git repo, dirty state, detached HEAD, non-git dir, nonexistent dir), verifies 2-line output and content (model name, cost format, progress bar chars); injects a mock cache file to test sess/week bar rendering; checks CLI help; ensures no console.log in statusline.js. All paths are __dirname-relative — safe to run from any cwd.

Read the full file on GitHub · 143 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. 2mo ago First seen · 143 lines · 2,296 tokens per session scan B df984e6c3036

Subscribe to this mod's changes

ccs CLAUDE.md is an instructions file published in the GitHub repository yusufalikync/ccs (4 stars, last pushed 7mo ago), licensed MIT. It adds 2,296 tokens to every session, about $0.0092 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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

microsoft/vscode · 9,715 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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens