kdeps-harness-invoke-example
v1.0.0kdeps harness: invoke-example
set harness / shelf harness
PurposeThe text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
LLM context: ~183 tokens when loaded (prompt or tool definition)
Where it runs
Part of the harness set, used in workflow and agent mode. The text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
- you type a prompt
- the agent loop builds the request
- the harness sections become the system promptharness/invoke-example
- the model answers
- the loop runs tools or replies
Loaded by: kdeps (agent loop), /settings, kdeps run, kdeps konfig export, kdeps knowledge build, kdeps konfig import
In the code: kdeps (agent loop)agent.Newagent.harnessText
Install
A kdeps asset: installed with the first-run profile that includes its set, or the first time a command needs it, and updated without a new release.
Pin a version with kdeps install harness/invoke-example@<version>.
Contents
- name
- invoke-example
- kind
- standalone
kdeps is a parser and an interpreter. It parses a matched <invoke>...</invoke> block out of your message at runtime and interprets it. Not your code interpreter. Writing the block is the call, not an example. If your backend has no native tool-call channel, the block is a LITERAL invoke block: write the characters <invoke> and </invoke> as literal text. Emit one block exactly like this (open tag and close tag, nothing else around it): <invoke name="bash_exec"> <parameter name="command">pwd && ls</parameter> </invoke> or, to read a file: <invoke name="read_file"> <parameter name="file_path">path/from/the/task</parameter> </invoke> Emit one such block and wait for the runtime's real result before answering.
version: 1.0.0
name: invoke-example
kind: standalone
body: |-
kdeps is a parser and an interpreter. It parses a matched <invoke>...</invoke> block out of your message at runtime and interprets it. Not your code interpreter. Writing the block is the call, not an example. If your backend has no native tool-call channel, the block is a LITERAL invoke block: write the characters <invoke> and </invoke> as literal text. Emit one block exactly like this (open tag and close tag, nothing else around it):
<invoke name="bash_exec">
<parameter name="command">pwd && ls</parameter>
</invoke>
or, to read a file:
<invoke name="read_file">
<parameter name="file_path">path/from/the/task</parameter>
</invoke>
Emit one such block and wait for the runtime's real result before answering.
Versions
| Version | Published | Status |
|---|---|---|
| 1.0.0 | 10/11/2026 | active |
Details
- Author
- kdeps
- License
- Apache-2.0
- Latest Version
- 1.0.0
- Published
- 10/11/2026