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/yusufalikync/ccs/claude-mdgit clone --depth 1 https://github.com/yusufalikync/ccsWrote 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/yusufalikync/ccs/claude-md)<a href="https://agentmods.dev/instructions/yusufalikync/ccs/claude-md"><img src="https://agentmods.dev/badge/instructions/yusufalikync/ccs/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.02296 | $0.02296 |
| Opus 5 | $0.01148 | $0.01148 |
| Sonnet 5 | $0.00459 | $0.00459 |
| Haiku 4.5 | $0.00230 | $0.00230 |
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 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.
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) 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.jsfiles useimport/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.
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 · 143 lines · 2,296 tokens per session scan B df984e6c3036
ccs CLAUDE.md is an instructions file published in the GitHub repository yusufalikync/ccs (2 stars, last pushed 5mo ago), licensed MIT. It adds 2,296 tokens to every session, about $0.0115 per session on Opus 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.
Other instructions, from other repositories
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
my-claude-skills CLAUDE.md
Instructions for brody-0125/my-claude-skills, covering claude code skills repository, validation commands, sub-kopring-engineer: kotlin/java 코드 컨벤션 검증, numerical: 수치 연산 코드 검증 and sub-test-engineer: 문서 일관성 검증.
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).