Authoritative Command Code product knowledge — slash commands, CLI options, permissions, skills, custom agents, MCP servers, hooks, memory, headless mode, plan mode, checkpoints, sessions, the model catalog, taste, pricing, and troubleshooting. Use when the user asks how Command Code works, how to configure or extend it, which models exist, or when you need product facts to answer a "can Command Code do X" question. Do NOT search the codebase for product behavior — read the reference files he...
Pro scans all 13 files and shows the line behind each finding
Scanned 9/19/2026
npx -y skills add Nir-Bhay/commandcode-cursor-proxy --skill command-code-knowledge --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Command Code Knowledge?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nir-bhay-command-code-knowledge)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: command-code-knowledge
description: Authoritative Command Code product knowledge — slash commands, CLI options, permissions, skills, custom agents, MCP servers, hooks, memory, headless mode, plan mode, checkpoints, sessions, the model catalog, taste, pricing, and troubleshooting. Use when the user asks how Command Code works, how to configure or extend it, which models exist, or when you need product facts to answer a "can Command Code do X" question. Do NOT search the codebase for product behavior — read the reference files here instead.
---
# Command Code Knowledge
You are answering a question about Command Code itself (or configuring/extending it). The
`reference/` directory next to this file IS the authoritative product documentation — it is
generated from the public docs (commandcode.ai/docs) and from the same registries that drive
the product (`/model` catalog, billing tables, slash-command menu), so it can never be more
wrong than the product. Never guess and never grep the codebase for product behavior: open
the matching reference file.
## How to use this skill
1. Pick the reference file(s) below that cover the question and read them.
2. Answer from what they say; quote exact ids, flags, paths, and settings keys verbatim.
3. Model questions (which model, exact ids, context windows, efforts, prices): read
`reference/models.md` — ids there are EXACT; never invent a model id.
4. Anything about the help surface (slash commands, keyboard shortcuts, CLI flags, taste,
FAQ, pricing links): `reference/product-help.md` — the same document the
`get_command_code_knowledge` tool serves.
5. Building a mod (a loadable ModApi plugin)? Switch to the `mod-builder` skill — it has
the mods reference and runnable examples.
## Reference index
<!-- generated:reference-index:start -->
- `reference/permissions.md` — Permissions
- `reference/skills.md` — Agent Skills
- `reference/mcp.md` — MCP Servers
- `reference/hooks.md` — Hooks
- `reference/custom-slash-commands.md` — Slash Commands
- `reference/custom-agents.md` — Custom Agents
- `reference/memory.md` — Memory
- `reference/headless.md` — Headless Mode
- `reference/plan-mode.md` — Plan Mode
- `reference/sessions.md` — Sessions & Checkpoints
- `reference/models.md` — Command Code Models
- `reference/product-help.md` — Product help (slash commands, CLI, taste, FAQ, pricing)
<!-- generated:reference-index:end -->
## Verify your answer
- Ids and flags must appear verbatim in a reference file — if you cannot find it, say so
rather than inventing it.
- When the user should run something, prefer the exact command a reference file shows
(e.g. `cmd mcp add --transport http …`, `cmd --mod ./file.ts`).
- These files regenerate from the docs via `pnpm generate:knowledge`; if the user reports a
mismatch with the live product, the public docs at https://commandcode.ai/docs are the
place to check.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!