A project setup command for cc-suite, which connects several coding assistants and their shared tools to one codebase.

Use it when starting cc-suite in a project or rebuilding its initial setup. It creates bridge files, shared skill links, tool-server registrations, and project configuration.

It avoids manually creating configuration files and connecting each assistant, skill, hook, and tool server. It gives the project the files needed for cc-suite to work.

init — Command by xiaolai

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 commands/xiaolai/cc-suite/init

Clone the repo

git clone --depth 1 https://github.com/xiaolai/cc-suite

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,476 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5	$0.00037	$0.04476
Opus 5	$0.00018	$0.02238
Sonnet 5	$0.00007	$0.00895
Haiku 4.5	$0.00004	$0.00448

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

Security

Grade A, and why

init 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 2d 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.

commands/init.md · 422 lines

How it starts

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

CC-Suite Init

Set up cc-suite for the current project. This command leaves the project with every bridge artifact in place — anything /cc-suite:repair would re-create is created here first. The sub-routines, in order:

Project config — generates .cc-suite.md with your preferred audit settings
Bridge init — creates AGENTS.md, CLAUDE.md (@AGENTS.md), .codex/config.toml, and the .gitignore block
Skills bridge — exposes cc-suite's plugin skills via .claude/skills/cc-suite and .agents/skills
MCP registration — adds the codex-cli MCP server to .mcp.json and mirrors project MCP servers into .codex/config.toml and .agents/mcp_config.json
Claude MCP registration — adds the claude-code MCP server (claude-octopus) to .codex/config.toml
Hooks bridge — mirrors .claude/settings.json hooks into .codex/hooks.json (no-op if there are no hooks)
Advisor agents bridge — registers any declared .cc-suite/agents/*.md in Claude's .mcp.json and Codex's .codex/config.toml; the agy projection is refreshed by the MCP bridge (no-op if there are no agents)

Workflow

Step 1: Check for existing config

Check if .cc-suite.md already exists in the current working directory.

If it exists, read it and ask:

AskUserQuestion:
  question: "A .cc-suite.md already exists. What would you like to do?"
  header: "Config"
  options:
    - label: "Add missing sections (Recommended)"
      description: "Non-destructively top up the config with any new cc-suite-managed sections (e.g. Enabled Tools), preserving your existing settings, then re-run the non-interactive bridge steps so any missing artifacts are created"
    - label: "Show current config"
      description: "Display the current settings"
    - label: "Regenerate"
      description: "Replace with a fresh config — asks the questions again and discards customizations"
    - label: "Cancel"
      description: "Keep the current config as-is"

If "Add missing sections" → run the migration and report what it added:

Read the full file on GitHub · 422 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.

2d ago First seen · 422 lines · 37 tokens per session scan A bfc0557d6621

Subscribe to this mod's changes

init is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 23d ago), licensed ISC. It adds 37 tokens to every session and 4,476 once invoked, about $0.0002 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.

init

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CC-Suite Init

Workflow

Step 1: Check for existing config

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement