ccmanager CLAUDE.md

Repository instructions for ccmanager, a TypeScript command-line application with a user interface.

In plain words
What is it for?
Use them when changing ccmanager's components, services, hooks, utilities, CLI, tests, or compiled output.
Why use it?
They describe where code and tests belong and list the commands for development, type checking, linting, building, and releases.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/kbwo/ccmanager/claude-md
Clone the repo
git clone --depth 1 https://github.com/kbwo/ccmanager
Per session 595 This file is loaded in full into every session.
When invoked 595 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00595 $0.00595
Opus 5 $0.00298 $0.00298
Sonnet 5 $0.00119 $0.00119
Haiku 4.5 $0.00060 $0.00060

Measured 3d ago against content hash c9f12892840e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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 · 35 lines

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 in src/components/, domain logic in src/services/, shared hooks in src/hooks/, and utilities/constants in their respective folders.
  • Tests sit beside the code they cover (e.g., Menu.tsx and Menu.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 dev launches TypeScript in watch mode for rapid feedback.
  • bun run build produces release-ready output in dist/.
  • bun run start executes the compiled CLI (dist/cli.js) for manual smoke tests.
  • bun run lint, bun run lint:fix, and bun run typecheck enforce style and typing before review.
  • bun run test runs the Vitest suite once; combine with bun run prepublishOnly before 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/ and services/ 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.ts or *.test.tsx); mirror the folder containing the behavior.
  • Use Ink Testing Library utilities for interactive components; stub terminal state as needed.
  • bun run test outputs coverage summaries (text, JSON, HTML under coverage/); maintain or improve coverage when changing core flows.
  • Name test suites after the component or service under test for easy grepping.

Read the full file on GitHub · 35 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. 3d ago First seen · 35 lines · 595 tokens per session scan A c9f12892840e

Subscribe to this mod's changes

ccmanager CLAUDE.md is an instructions file published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed 3d ago), licensed MIT. It adds 595 tokens to every session, about $0.0030 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