Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sd0xdev/sd0x-harnessnpx agentmods add skills/sd0xdev/sd0x-harness/doc-reviewWrote 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/sd0xdev/sd0x-harness/doc-review)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/doc-review"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/doc-review.svg" alt="Measured on agentmods" 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.00056 | $0.03260 |
| Opus 5 | $0.00028 | $0.01630 |
| Sonnet 5 | $0.00011 | $0.00652 |
| Haiku 4.5 | $0.00006 | $0.00326 |
Grade A, and why
doc-review 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Review Skill
Trigger
- Keywords: review doc, document review, tech spec review, review-spec, doc-refactor, streamline doc
When NOT to Use
- Code review (use
codex-code-review) - Test coverage review (use
test-review) - Just want to read a document (use Read directly)
Commands
| Command | Description | Use Case |
|---|---|---|
/codex-review-doc |
Codex reviews .md docs | Document changes |
/review-spec |
Review tech spec | Spec confirmation |
/doc-refactor |
Streamline documents | Doc too long |
/update-docs |
Research & update docs | After code change |
Workflow: /codex-review-doc
Target set → Deterministic checks → Resolve profiles + batches → Codex review per batch → Rating table + Gate → Loop
All changed .md in one change are one review plan. The plan is the unit; it holds one or more
physical batches, and within the budget it is exactly one batch and therefore one dispatch. Reviewing
file-by-file is what this workflow replaced — it multiplied a three-file change into three whole-
document reviews.
Step 1: Determine the Target Set
| Condition | Action |
|---|---|
| Paths specified | Use them — all of them, as one plan |
| No path | git diff --name-only HEAD and untracked, filtered to .md |
| Nothing changed | Report it and stop; there is no document to review |
Never narrow a multi-file change to one file, and never ask the user to pick one. A file the plan drops is a file nothing reviewed.
Step 2: Deterministic Checks First
node scripts/check-doc-links.js --root "$(git rev-parse --show-toplevel)" <changed .md paths>
Resolves the repo-local file links it can classify, prints the ones that do not resolve, and
prints unresolved — how many link shapes it declined to classify. Heading fragments are out of
scope: [x](#frag) is dropped uncounted the way an external URL is, and [x](./a.md#frag) is
checked as a link to a.md alone. A dead #fragment is therefore not a finding this step
establishes, and the reviewer is free to raise one.
What ships with it
2 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.
- 2d ago Changed · -1 lines dce8805f38f5
- 7d ago First seen · 243 lines · 56 tokens per session scan A dd38acb4067c
doc-review is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 3,260 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 skills, from other repositories
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.
planning
Planning discipline for creating execution plans and decision RFCs. Covers task decomposition, context references, validation levels, risk-based testing, ADR format, plan completeness gate, and functionality flow mapping. Loaded by planner agent.