ak commands
ak commands
Browse and manage individual local Claude-style slash-command templates without treating them as a runtime-neutral kit install.
Use ak commands as the entry point for listing, searching, inspecting,
installing, or removing one Markdown command template. Running the group itself
prints help and exits 0; it does not scan or modify either inventory.
Catalog model
This family compares two local filesystem inventories:
| Inventory | Default location | Shape |
|---|---|---|
| Available | ./kits/<kit>/commands/**/*.md | Recursive source tree; nesting determines the Claude-style slash name. |
| Installed | ~/.claude/plugins/<kit>/commands/<flat-name>.md | Flat per-kit copies in the user plugin root. |
AGENTKIT_KITS_DIR replaces ./kits, and AGENTKIT_PLUGIN_DIR replaces
~/.claude/plugins. No subcommand queries a remote catalog, account,
entitlement service, or verified cache.
A source path such as ckm/write/good.md has slash name ckm:write/good and
canonical asset name ckm-write-good. The ref used by these commands is
therefore <kit>/<flat-name>, not the slash invocation text.
Usage
ak commandsThe group accepts no positional arguments. --json does not convert group help
to JSON; use a runnable leaf command for structured output.
Subcommands
| Command | Outcome | Disk effect |
|---|---|---|
ak commands list | Merge installed and locally available templates. | Read-only. |
ak commands search <query> | Rank the merged inventory by metadata and slash name. | Read-only. |
ak commands show <kit>/<command> | Show one installed or available record. | Read-only. |
ak commands install <kit>/<command> | Flatten and copy one local source template. | Writes one file. |
ak commands remove <kit>/<command> | Delete the exact flat installed file. | Removes one file when present. |
There are no Cobra command aliases in this group. Refs accept ak:<command>,
ake:<command>, and akm:<command> as short forms for core, engineer, and
marketing. Prefer canonical refs in scripts.
Runtime and ownership boundary
These commands manage individual files under the Claude plugin root. They do not emit a complete project or user kit route, activate a plugin, adapt a command for another runtime, update lifecycle ownership, or create recovery snapshots. Codex has no native equivalent for these Claude-style commands; installing a file here does not create one.
Use ak kit init for reviewed runtime-specific installation. Treat the source
and destination roots as trusted local data, especially when environment
variables redirect them.
Output and exits
Leaf successes write human output or one JSON envelope to stdout. Errors go to stderr; JSON execution errors use the shared error envelope, while flag-parse errors can remain plain text. The family has no prompt, stdin protocol, NDJSON, network, auth, or entitlement flow.
The group help path exits 0. Leaf commands use command-local exits including
2 for a malformed ref, 5 for a missing record or source, and 6 for an
existing destination without --force.