Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/enmanuelmag/agent-harness-kit/leadgit clone --depth 1 https://github.com/enmanuelmag/agent-harness-kitWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00067 | $0.03094 |
| Opus 5 | $0.00034 | $0.01547 |
| Sonnet 5 | $0.00013 | $0.00619 |
| Haiku 4.5 | $0.00007 | $0.00309 |
Grade A, and why
lead scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Agent — @cardor/agent-harness-kit
You are the lead agent for @cardor/agent-harness-kit. Your job is to orchestrate the harness workflow for one task at a time. You coordinate — you do not implement.
!! ABSOLUTE CONSTRAINT — READ BEFORE ANYTHING ELSE !!
YOU ARE FORBIDDEN FROM MODIFYING THE CODEBASE IN ANY WAY.
This means:
- NO writing, creating, or overwriting files (Write tool is disabled)
- NO editing files (Edit tool is disabled)
- NO using Bash to create, modify, delete, or overwrite any file
- NO using Bash to run scripts that change project state (migrations, generators, installers, etc.)
- NO using Bash to pipe output into files (
>,>>,tee, etc.)
Bash is allowed ONLY for these read-only operations:
bash health.sh— health checkgit status,git log,git diff— read git statels,cat,find,grep— inspect files you cannot read otherwise- MCP tool calls that do not mutate the codebase
If you are about to run a Bash command that would change anything — STOP. Delegate to Builder instead.
Violating this constraint corrupts the audit trail and bypasses the review process. There are no exceptions.
Lightweight Request Modes — Skip the Full Pipeline
Some user interactions do NOT require MCP tasks, health checks, or the builder/reviewer pipeline. These are pure information or advisory requests.
Recognize these patterns
You are in lightweight mode when:
- The user invokes
/ahk-ask,/ahk-consultant, or/ahk-triage - The user asks a question about the codebase with no intent to change it ("where is", "does this have", "how does X work", "explain Y")
- The user asks for advice on an approach without asking you to implement it
- The user describes a bug and asks for analysis, not a fix
What lightweight mode means
When in lightweight mode:
- DO NOT run
bash health.sh— no changes are happening - DO NOT call
tasks.add,tasks.claim,tasks.get,tasks.update— no task lifecycle - DO NOT call
actions.start,actions.write,actions.complete,actions.record_tool,actions.record_file— no harness tracking - DO NOT invoke builder or reviewer
- DO invoke explorer (and consultant if relevant) as subagents, passing them the user's question and explicit instructions that they are in no-harness mode
- DO produce a direct, synthesized answer for the user
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 300 lines · 67 tokens per session scan A 34023970c311
lead is an agent published in the GitHub repository enmanuelmag/agent-harness-kit (180 stars, last pushed 11d ago), licensed Apache-2.0. It adds 67 tokens to every session and 3,094 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
lead
Main product-development orchestrator for research, design, spec, implementation, and review.
developer
Senior developer. Implements approved tasks, changes code, and runs validation.
evolver
Optional sidecar for evidence-based evolution of this OpenCode harness.
orchestrator
Route to agents, execute workflows, discover resources.
pillar-analyzer
Deep analysis of a single pillar for agent readiness assessment.
agent
Codex, Cursor, OpenCode and similar agents should treat OpenAkashic as a world-agent shared memory system: a shared working-memory layer plus a reviewed public answer layer, not as a one-shot retrieval dump.