Busabase x Knowledge Base for Kilo CodeKnowledge Base for Kilo Code
Kilo Code lets teams define agents with prompts, models, modes, tool permissions, and project or organization scope. That turns workflow design into configuration, but a configured delegate still returns a proposal that needs an owner and evidence.
MAP
A Kilo agent can be scoped precisely; the result still needs a separate acceptance decision.
Kilo Code lets teams define agents with prompts, models, modes, tool permissions, and project or organization scope. That turns workflow design into configuration, but a configured delegate still returns a proposal that needs an owner and evidence.
Prompt, model, mode, steps, color
Isolated session, task delegation, tool permissions
SKILL.md metadata and on-demand instructions
Allow, ask, deny, ordered glob rules
01 · Knowledge Base for Kilo Code
Primary, subagent, and all modes express delegation intent
Kilo Code lets teams define agents with prompts, models, modes, tool permissions, and project or organization scope. That turns workflow design into configuration, but a configured delegate still returns a proposal that needs an owner and evidence.
| Custom agent | Prompt, model, mode, steps, color | A behavior profile with a defined scope |
|---|---|---|
| Subagent | Isolated session, task delegation, tool permissions | A delegated worker whose result returns to the parent |
| Skill | SKILL.md metadata and on-demand instructions | A portable procedure, not an accepted outcome |
| Permission | Allow, ask, deny, ordered glob rules | Execution control, not factual validation |
02 · Knowledge Base for Kilo Code
Permission rules can restrict edit, bash, read, task, and other tools
A Kilo agent can be scoped precisely; the result still needs a separate acceptance decision.
A behavior profile with a defined scope
A delegated worker whose result returns to the parent
A portable procedure, not an accepted outcome
Execution control, not factual validation
03 · Knowledge Base for Kilo Code
Project and organization-managed agents have different owners
Knowledge Base for Kilo Code: Primary, subagent, and all modes express delegation intent; Permission rules can restrict edit, bash, read, task, and other tools; Project and organization-managed agents have different owners.
kilo-code_1Prompt, model, mode, steps, color · A behavior profile with a defined scopekilo-code_2Isolated session, task delegation, tool permissions · A delegated worker whose result returns to the parentkilo-code_3SKILL.md metadata and on-demand instructions · A portable procedure, not an accepted outcomekilo-code_4Allow, ask, deny, ordered glob rules · Execution control, not factual validationEVIDENCE
Knowledge Base for Kilo Code: inspect the boundary
Primary, subagent, and all modes express delegation intent Permission rules can restrict edit, bash, read, task, and other tools Project and organization-managed agents have different owners
kilo-code_1Custom agent: Prompt, model, mode, steps, color; A behavior profile with a defined scopekilo-code_2Subagent: Isolated session, task delegation, tool permissions; A delegated worker whose result returns to the parentkilo-code_3Skill: SKILL.md metadata and on-demand instructions; A portable procedure, not an accepted outcomekilo-code_4Permission: Allow, ask, deny, ordered glob rules; Execution control, not factual validation
ACCEPTANCE
Knowledge Base for Kilo Code: execution is not acceptance
A Kilo agent can be scoped precisely; the result still needs a separate acceptance decision.
Verify Prompt, model, mode, steps, color before accepting A behavior profile with a defined scope.
Verify Isolated session, task delegation, tool permissions before accepting A delegated worker whose result returns to the parent.
Verify SKILL.md metadata and on-demand instructions before accepting A portable procedure, not an accepted outcome.
Verify Allow, ask, deny, ordered glob rules before accepting Execution control, not factual validation.
FAQ
Knowledge Base for Kilo Code: practical questions
A Kilo agent can be scoped precisely; the result still needs a separate acceptance decision.
Does a custom agent own the knowledge it produces?
No. It owns an execution profile. The parent or designated reviewer decides whether the result is reusable.
Are permission rules approval rules?
They control tool access and prompts. They do not verify that a generated claim is correct.
Should organization agents be copied into a shared database?
Record the owner and definition version, but keep the operational definition in Kilo configuration and review cross-system facts separately.
Does a Skill become trusted when it is discovered?
Discovery exposes metadata. The Agent loads instructions on demand; the procedure and its output still have different review paths.
NEXT
A Kilo agent can be scoped precisely; the result still needs a separate acceptance decision.
Kilo Code lets teams define agents with prompts, models, modes, tool permissions, and project or organization scope. That turns workflow design into configuration, but a configured delegate still returns a proposal that needs an owner and evidence.