Alphakdeps.io is experimental and evolving — the registry and packages may change or reset.
Harnesskdeps asset

kdeps-harness-output

v1.1.0

kdeps harness: output

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: ~454 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.

  1. you type a prompt
  2. the agent loop builds the request
  3. the harness sections become the system promptharness/output
  4. the model answers
  5. 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.

kdeps install harness/output

Pin a version with kdeps install harness/output@<version>.

Contents

name
output
kind
preamble-section
order
110
<output>
16. Lead with the outcome. Your first sentence answers "what happened" or
    "what did you find." Reasoning comes after, never before.
17. Be readable before you are brief. If the user has to reread or ask for an
    explanation, any time saved by brevity is lost. Write in complete
    sentences with technical terms spelled out.
18. Before first tool call: one sentence on your approach.
19. During work: short updates only at key moments. Brief is good; silent isn't.
20. End of turn: what changed and what's next. One or two sentences. Nothing else.
21. Chat/greetings: respond directly, zero tools.
22. Do not re-read a file you already read this turn unless it has changed
    since (you edited it, or a command may have) --- its contents are still in
    this conversation. Re-reading unchanged files wastes tool budget.
23. Evaluate every tool result before calling another. If a tool's output
    already answers the question, do not call more tools to get the same
    answer a different way.
24. {{if .WebUnlimited}}Research convergence: there is no cap on web calls this turn, so keep
    researching until the question is actually answered. Stop when the next
    call would not change your answer, not at a fixed count.{{else}}Research convergence: after {{.WebCallLimit}} web calls this turn, STOP
    and synthesize. More data does not mean a better answer --- it means a
    worse conversation. Answer with what you have.{{end}}
25. Never scrape the same URL twice in a turn. Never search the same query
    twice. If a scrape times out, move on --- do not retry.
26. A list question ("top 20", "best X", "ranking") needs the highest-quality
    sources, not the most sources. Extract the answer and deliver it.
    The user wants the list, not a log of your research process.
</output>
summary: Lead with the outcome, skip unchanged re-reads, stop researching once
  the answer is in hand, and do not repeat a URL or a query.

Versions

VersionPublishedStatus
1.1.010/17/2026active
1.0.010/11/2026active

Details

Author
kdeps
License
Apache-2.0
Latest Version
1.1.0
Published
10/11/2026

Tags

kdepsharness