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 skills add cilidinezy-commits/doc-harness --skill kimi-skillgit clone --depth 1 https://github.com/cilidinezy-commits/doc-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cilidinezy-commits/doc-harness/kimi-skill)<a href="https://agentmods.dev/skills/cilidinezy-commits/doc-harness/kimi-skill"><img src="https://agentmods.dev/badge/skills/cilidinezy-commits/doc-harness/kimi-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cilidinezy-commits/doc-harness/kimi-skill"><img src="https://agentmods.dev/badge/skills/cilidinezy-commits/doc-harness/kimi-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00272 | $0.02159 |
| Opus 5 | $0.00136 | $0.01079 |
| Sonnet 5 | $0.00054 | $0.00432 |
| Haiku 4.5 | $0.00027 | $0.00216 |
Grade A, and why
doc-harness 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Harness — Document-Based Project Control
Doc Harness creates and maintains five status documents per project that enable any agent or human to understand and resume project work purely from reading files — no external memory needed.
Core principle: "Write It Down or Lose It" — all information in context is temporary. If it is not written to a file and registered in FILE_INDEX, it will be lost.
The Five Documents
| Document | Role | Answers |
|---|---|---|
| CLAUDE.md | Project entry point | "What is this project? What are the rules? Where do I start?" |
| CURRENT_STATUS.md | Active state | "What just happened? What's happening now? What's next?" |
| FILE_INDEX.md | File catalog | "What files exist, what are they, and where are they?" |
| WORKLOG.md | Permanent history | "What exactly happened in phase 2, three weeks ago?" |
| DOC_HARNESS_SPEC.md | Complete reference | Full specification for unusual situations |
Metaphor: A project in motion is like a moving car.
- Tire Tracks (Recent Completed) — the road behind
- Car Body (Current Work) — where you are right now
- Headlights (Next Steps) — where you're going
- Driving Manual (Working Principles) — rules for this road
Natural-Language Commands
Kimi has no slash commands. Use the table below to map user requests to the correct procedure.
| User says | Procedure | See |
|---|---|---|
| "Set up doc-harness" / "init project docs" / "create status documentation" | Init — create the five documents for a new or existing project | references/init.md |
| "Check documentation health" / "audit project docs" / "run a health check" | Check — audit file health and reflect on principles | references/check.md |
| "Sync project state" / "update status docs" / "catch up documentation" | Sync — repair drift, refresh dates, register missing files | references/sync.md |
| "Save everything" / "flush context" / "prepare for compact" / "ensure nothing is lost" | Flush — emergency save: extract all important context into documents. Runs five phases: (A) sync, (B) context inventory, (C) write and register, (D) verification, (E) flush marker. Phases B and C are the defining feature — they scan context for information that exists only in memory and write it to files. Without Phase B and C, flush has failed and is indistinguishable from sync. | references/flush.md |
| "Resume this project" / "continue work" / "where were we" / "back to project" / "pick up where we left off" / "what's the current status" | Resume — structured state recovery. Execute Recovery Chain, produce Recovery Report, verify understanding before continuing. Four phases: (A) Recovery Chain, (B) Recovery Report synthesis, (C) Understanding Verification, (D) Resume decision. | references/resume.md |
| "Recall" / "remember" / "find in docs" / "search project docs" / "where did we discuss" / "why did we decide" / "what is the current plan" | Recall — retrieve information from registered documents along the Doc Harness hierarchy | references/recall.md |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 139 lines · 272 tokens per session scan A e13fc1c59d66
doc-harness is a skill published in the GitHub repository cilidinezy-commits/doc-harness (4 stars, last pushed 9d ago), licensed MIT. It adds 272 tokens to every session and 2,159 once invoked, about $0.0014 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-31.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
harness-step3-session-management
A project setup for keeping an agent’s work state in files between separate chat sessions. It creates a task list, a progress summary, and a script for checking the project environment.
project-context-loader
Load relevant memory, decisions and contacts for the current project at the start of a session.
sweep-now
Run the three read-mostly vault sweeps for stale tracker items, dormant-note candidates, and broken wikilinks, then append one dated result to SWEEPLOG.md.
operator-setup
The AIgent first-run operator-business interview. Learn the operator's business in three plain questions, write the first memory, and play back a briefing that reads personal, not templated. This is the "it remembers me" moment. A distinct skill that LAYERS ON TOP of the base /setup (which is left intact), it does not…
continue
Use when you need the Codex Copilot equivalent of Claude Copilot /continue: resume paused or previous work from tc tasks, work products, memory, and stream context.