---

name: kilocode-cli description: Use Kilo Code CLI as a subagent. Lets the main agent prompt Kilo Code CLI from the terminal in headless mode with the kilo command, and send the goal, the decisions and the scope with the task. Use when the user asks to delegate work to Kilo Code CLI, when a task needs a second independent agent, or when a plan needs a fresh perspective. allowed-tools:

• Bash
• Read
• Write
• Grep
• Glob

---

Kilo Code (subagent / task delegation)

What is it

This skill teaches your agent to use an agent from another vendor as a subagent.

Almost every coding agent has a headless mode. Headless mode runs the agent from the terminal with one command and returns the answer to stdout. This skill gives the command pattern for one such agent, and the protocol to transfer enough context with the task.

You stay the main agent. You keep the plan, the decisions and the conversation with the user. The subagent does one bounded task and reports back.

When to delegate

• The user asks for it. The user names another agent, or asks for a second opinion.
• Large or multi-step work. The task covers several files, phases or checkpoints.
• Code review with a fresh mind. Another agent reviews the work with a different lens and no memory of the decisions that produced it.
• Planning that needs different ideas. A second agent proposes options that you did not consider.
• An internal council. Several subagents answer the same question, and you compare the answers.
• Deep research. The other CLI has web search, web extraction or browser automation.
• Background investigation. A long task runs in the background while you continue in the foreground.

When not to delegate

• Small or single-step tasks. One or two edits, or a short explanation, are faster in this thread.
• Tight feedback loops. The user wants quick back-and-forth in one conversation.
• Secrets or policy-sensitive work. Do not pipe credentials into a subagent. Redact first.
• Context you already hold. Repeating the whole plan in a prompt adds no value.
• Low return on investment. If writing the handoff costs more than doing the edit, do the edit.
• Work that needs high precision and full judgement. A subagent without your context will break a task that depends on a detail only this session knows.

Delegation and context transfer protocol

An isolated subagent saves tokens, but it splits the story. The subagent does not see this conversation. It has no memory of the goal you agreed with the user, the decisions you already made, or the paths you agreed not to touch. A poor handoff causes misread tasks, wrong assumptions about the stack or the style, and wasted edits.

Treat every call as stateless delegation: the subagent keeps nothing between calls, so each command must carry its own state. A good handoff happens when you keep these practices in mind:

• Shared state handoff. The prompt carries the original goal, the decisions already made, and the explicit scope, to bridge the subagent's missing session history.
• Contextual preservation. The high-volume work stays in the isolated process, so the bulk never enters this conversation and no "split story" forms from missing history.
• Result reconciliation. What comes back is folded into this thread afterwards, so there is a single source of truth.

Write the prompt as a transfer of shared state, not as a title. Include all six fields:

Include	Why
Goal	The same objective as the user, not only the immediate micro-task.
Decisions	Framework, patterns, naming, "use X not Y" — anything that would otherwise be guessed wrong.
Scope	The absolute paths and modules to touch, and the areas to leave alone. A relative path may not resolve where you expect.
Constraints	Performance, accessibility, compatibility, review gates, "no new dependencies".
Verification	The exact command the subagent must run and pass before it returns.
Output	For example: "report only, no edits", "apply edits with a minimal diff", "list the files changed".

Prefer sequential delegations with explicit carry-over. Parallel runs diverge unless every run gets the same briefing.

Run the subagent in the mode that does the work without asking for approval. Headless mode has nobody to answer a permission prompt. Any mode that stops to ask will stall, or return an empty answer with a success exit code. Each CLI names this mode differently — take the flag from the vendor card below.

Never call a subagent in plan mode. Many CLIs have a plan or read-only mode. That mode makes the other agent write a plan for itself, which is not what you asked for: you want its work or its answer, and you keep the planning. Plan mode also waits for someone to approve that plan, so the run comes back with nothing. If you want no file changes, keep the auto-approving mode and write "report only, no edits" in the Output field. Do not use plan mode to make a run read-only.

After the subagent returns:

• Report to the user. Give a short summary. Do not paste long logs unless the user asks.
• Reconcile the context. Record the decisions it made, the files it changed, and the open risks, so this session stays the single source of truth.

CLI failure modes

Every vendor has its own terminal rules. A headless run fails quietly more often than it fails loudly.

• Wrap the call in an external timeout. A headless CLI can stall before its own timeout starts.
• Exit code 0 is not success. If stdout is empty, treat the run as failed and read stderr. A permission the CLI could not ask for, and a prompt that never arrived, both look like success.
• Never carry a flag habit from one CLI to another. The same short flag means different things in different tools. In OpenCode, -p is --password: passing a prompt to it empties the message and the run waits on stdin forever. Confirm every flag against the CLI's own --help.
• An unrecognized-flag error means this skill is stale, not that the task is impossible. Read --help, continue with the flags that exist, and tell the user which line in this file is wrong.

Vendor card

Binary and prompt form

• Binary: kilo (the package also installs kilocode, which points at the same file)
• Prompt form: positional, after the run subcommand: kilo run "prompt" (kilo run [message..] — the message is a variadic positional argument). A bare kilo opens the interactive interface and never returns.
• The verified trap: -p is --password — basic auth for an attached server, defaulting to KILO_SERVER_PASSWORD. This is the same trap OpenCode has, because Kilo Code is built on OpenCode. Writing kilo run -p "GOAL: ..." feeds the whole prompt into basic auth and leaves the message empty, so the run produces nothing. Always pass the prompt positionally.

Headless and output flags

Need	Flag
Run once and exit	run "prompt"
Formatted output	--format default
Raw JSON events	--format json
Diagnostics to stderr	--print-logs, --log-level DEBUG|INFO|WARN|ERROR
Working directory	--dir <path>
Attach a file to the message	-f, --file <path>
Reasoning effort	--variant <provider-specific value>
Continue a session	-c/--continue, or -s/--session <id>
Skip external plugins	--pure

There is no --timeout on kilo run and no documented default limit, so wrap long calls in an external timeout. There is also no --quiet.

Do not pass -i/--interactive; it switches the run to an interactive split-footer mode.

Approvals and permissions

--auto is documented as "auto-approve permissions that are not explicitly denied (dangerous!)" and its default is false. Always pass it. Without --auto a non-interactive run cannot prompt, so it auto-rejects any permission request and exits 1 with a stderr diagnostic naming the cause — the task will not have completed.

--auto is not a blanket bypass: it respects the configured auto-approval settings, and anything not auto-approved is still refused. A "deny" rule always wins. A full bypass is a config-level change ({"permission": "allow"} in the user's kilo.jsonc), which is the user's call, not yours.

Never select a plan-style agent with --agent. --agent chooses which configured agent runs the task. A planning agent writes a plan for itself and waits for approval, which headless mode cannot give. Keep the default agent and write "report only, no edits" in the Output field when you want no file changes.

Models and how to list them

Run kilo models for the identifiers this install accepts, optionally filtered by provider with kilo models <provider>. Select with -m/--model <provider/model>. Credentials are managed with kilo auth (alias kilo providers).

If the user names a model, use it. Otherwise ask the binary first. For capability and price comparisons, check Artificial Analysis and the vendor's own documentation.

Command pattern

kilo run "GOAL: [goal] | DECISIONS: [decisions] | SCOPE: [absolute paths] | CONSTRAINTS: [constraints] | VERIFICATION: [test_command] | OUTPUT: [format]" \
  --auto --model <provider/model> --dir /absolute/path/to/repo --print-logs 2>&1

For a long run, prefer backgrounding the call and watching the log over a blocking call with a guessed deadline:

kilo run "[prompt]" --auto --print-logs > /tmp/kilo-run.log 2>&1 &

Prompt examples

• Implement: kilo run "GOAL: [goal] | SCOPE: [absolute paths] | VERIFICATION: [test_command] | OUTPUT: files changed" --auto --dir /abs/repo
• Review: kilo run "GOAL: Review [scope] for [concerns] | CONSTRAINTS: do not edit any file | OUTPUT: findings with severity" --auto --format json --dir /abs/repo
• Investigate (background, watch log): kilo run "GOAL: Map how [feature] works | SCOPE: [absolute paths] | CONSTRAINTS: do not edit any file | OUTPUT: file:line map" --auto --print-logs > /tmp/kilo-run.log 2>&1 &

Docs and reference

• Flags, models, approvals, skills and paths: reference.md
• Vendor documentation: https://kilo.ai/docs/code-with-ai/platforms/cli
• Verified against kilo 7.7.6 by running --help, run --help and models --help on 2026-09-21. Flags came from the binary, not from documentation. A full delegation was not run, because that needs provider credentials.