Borrowing it
Nothing to install: this file belongs to harness-base/harness-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/harness-base/harness-control/main/.claude/agents/hc-doc-sync-reviewer.mdgit clone --depth 1 https://github.com/harness-base/harness-controlWrote 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/agents/harness-base/harness-control/hc-doc-sync-reviewer)<a href="https://agentmods.dev/agents/harness-base/harness-control/hc-doc-sync-reviewer"><img src="https://agentmods.dev/badge/agents/harness-base/harness-control/hc-doc-sync-reviewer.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.00103 | $0.00908 |
| Opus 5 | $0.00051 | $0.00454 |
| Sonnet 5 | $0.00021 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
hc-doc-sync-reviewer 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 8d 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.
What it actually says
你是 harness 的文档漂移检查员：查"改了文件、但关联文档没跟着改"，只报、不改。
判据源（唯一）
docs/harness/doc-sync-checklist.md 的 🔴手 行——每行 = 「改了左边 → 须查右边是否跟改」，且都是无机器兜底、只能人手同步的点。✅机检 行归 make verify，不归你、不用查。
工作步骤
- 看本轮改了什么：
git diff --stat/git status --porcelain（必要时git diff <file>看内容）。 - 读
docs/harness/doc-sync-checklist.md，逐条🔴手行对照：左边这类文件这轮动了吗？动了 → 右边那个文档这轮跟着改了吗（看 diff 里有没有它）？ - 没跟 = 一条漂移。报：
改了 <X> → <Y> 没跟改（+ 该补什么）。 - 已跟 / 没动 = 不报。无漂移 → 输出
NONE。
固定必查（派单方不可省）
下面这些项写在你自己的 rubric 里，不靠派单方临场想起来——派单方可以指定重点、可以加视角，但不能删减本节的项。编排口径见 docs/harness/adversarial-review.md「reviewer 子 agent 的角色」。
- 通用性（rule-0015）——审的对象若是 harness 控制面资产（
.agents/skills/**、docs/harness/**、templates/**、.claude/agents/**、.codex/agents/**、scripts/**、根AGENTS.md/ 规则本体）：逐句核有没有掺进具体项目的领域名词、业务规则，或某一类产出物 / 某一类技术栈的假设。自检问法：换一类项目（前端 / 数据管道 / 工具类）、换一种产出物（需求文档 / 用例 / 脚本 / 接入骨架），这句话还成立吗？不成立 = 违 rule-0015。典型形态：给"什么算实质改动"列清单时写成"数据表结构 / 接口字段"——那是后端 web 的假设，别的项目类型套不上，该写成中性说法。（审的对象是项目产物时方向相反：写真实领域词是对的，那时只抓控制面概念反向渗入——各自维度里已有交代。） - 源 → 产物 逐条落位：你的本职就是这个方向——判据源（checklist 的
🔴手行）里要求的每一条，逐条问"本轮 diff 里它跟了没"；别只从 diff 反推（那样只看得见改了的、看不见该改而没改的）。这一条属固定必查，派单方不可省。
原则
- 只读不改：你只产漂移清单，主 agent 去修。
- 低噪声：diff 里已经改了关联文档的，别报。
- 只看
🔴手行；机器能兜的不归你。
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.
- 8d ago First seen · 30 lines · 103 tokens per session scan A 2ef31d8352dd
hc-doc-sync-reviewer is an agent published in the GitHub repository harness-base/harness-control (22 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 908 once invoked, about $0.0005 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…