CCManager is a command-line application for managing multiple sessions of AI coding assistants across Git worktrees and projects. It is for developers working with tools such as Claude Code, Gemini CLI, Codex CLI, Cursor Agent, Copilot CLI, Cline CLI, OpenCode, and Kimi CLI, and the catalogue entries provide commands and instructions for its workflows.
Borrowing it
Nothing to install: this file belongs to kbwo/ccmanager. 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/kbwo/ccmanager/main/CLAUDE.mdgit clone --depth 1 https://github.com/kbwo/ccmanagerWrote 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/kbwo/ccmanager/claude-md)<a href="https://agentmods.dev/instructions/kbwo/ccmanager/claude-md"><img src="https://agentmods.dev/badge/instructions/kbwo/ccmanager/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/kbwo/ccmanager/claude-md"><img src="https://agentmods.dev/badge/instructions/kbwo/ccmanager/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.00595 | $0.00595 |
| Opus 5.5 | $0.00238 | $0.00238 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
ccmanager 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 1mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/holds all TypeScript sources; UI lives insrc/components/, domain logic insrc/services/, shared hooks insrc/hooks/, and utilities/constants in their respective folders.- Tests sit beside the code they cover (e.g.,
Menu.tsxandMenu.test.tsx), enabling focused updates. - Built artifacts compile into
dist/; keep changes out of version control. - Long-form notes and design references live under
docs/; sync any behavior changes here when relevant.
Build, Test & Development Commands
bun run devlaunches TypeScript in watch mode for rapid feedback.bun run buildproduces release-ready output indist/.bun run startexecutes the compiled CLI (dist/cli.js) for manual smoke tests.bun run lint,bun run lint:fix, andbun run typecheckenforce style and typing before review.bun run testruns the Vitest suite once; combine withbun run prepublishOnlybefore publishing to exercise the full pipeline.
Coding Style & Naming Conventions
- Follow the shared Prettier profile (
@vdemedes/prettier-config); formatting issues surface as ESLint errors. - Use modern TypeScript/React patterns, avoiding
any(rule enforced) and preferring explicit types for side-effectful functions. - Components and Effect-style services use PascalCase filenames; hooks start with
use. - Keep TUI prompts and commands in
constants/andservices/rather than inline JSX. - Prefer dependency-free helpers in
utils/so the CLI stays fast to load. - use logger class instead of console. e.g.
logger.info("This is info level log");
Testing Guidelines
- Write Vitest unit tests alongside new files (
*.test.tsor*.test.tsx); mirror the folder containing the behavior. - Use Ink Testing Library utilities for interactive components; stub terminal state as needed.
bun run testoutputs coverage summaries (text, JSON, HTML undercoverage/); maintain or improve coverage when changing core flows.- Name test suites after the component or service under test for easy grepping.
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.
- 1mo ago First seen · 35 lines · 595 tokens per session scan A c9f12892840e
ccmanager CLAUDE.md is an instructions file published in the GitHub repository kbwo/ccmanager (1,266 stars, last pushed 3d ago), licensed MIT. It adds 595 tokens to every session, about $0.0024 per session on Opus 5.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
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.