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 rules/sisyphussq/harness-template/harnessgit clone --depth 1 https://github.com/SisyphusSQ/harness-templateWrote 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/rules/sisyphussq/harness-template/harness)<a href="https://agentmods.dev/rules/sisyphussq/harness-template/harness"><img src="https://agentmods.dev/badge/rules/sisyphussq/harness-template/harness.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 | $0.00559 | $0.00559 |
| Opus 5 | $0.00280 | $0.00280 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
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 4d 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 协作规则
在本仓库工作时，先进入仓库内的 harness 控制面，再开始分析、计划、修改或收口。
渐进式读取
每个任务只默认读取：
AGENTS.md- 当前修改目录就近的目录级
AGENTS.md（如果存在）
之后按任务需要读取，不要预加载全部 Harness 文件：
- 状态机、Issue、review、验证或交付边界：
docs/harness/control-plane.md - 复杂任务：
.agents/PLANS.md - 真正写计划：
.agents/plans/TEMPLATE.md - 计划质量需要校准：
.agents/plans/EXAMPLE-implementation.md issue-provider=repo：docs/issues/README.md- 测试 runbook 任务：
docs/test/RUNBOOK_TEMPLATE.md - 手动工作流、多任务交接、review 或 lint：读取对应 prompt / guide
执行约束
- 非简单任务先按
.agents/PLANS.md与.agents/plans/TEMPLATE.md创建或更新计划。 - 实现型计划必须写真实代码入口、输入装配、组件职责、关键时序、错误处理和恢复路径。
- 不要用 harness 控制流替代业务实现架构或数据流说明。
- 项目真实约束写在
AGENTS.md；能机械执行的规则落实到项目 Makefile、lint 或 gate，没有执行入口时不要宣称已强制。 - 测试或自测文档使用
docs/test/RUNBOOK_TEMPLATE.md，只把脱敏结果摘要写入提交版文档。 - 收口前 macOS / Linux / Git Bash 优先执行
make harness-verify；Windows PowerShell 执行powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\harness\check.ps1。 - Bash / Git Bash 示例使用 POSIX 路径；PowerShell 示例使用
C:\path\to\repo或 UNC 路径，不自动互转。
真相边界
- Issue Tracker 是主协作真相。
- repo 是主执行真相。
- PR / MR 是次级代码叙事面。
.agents/state与.agents/runs是本地辅助运行面，不替代 Issue Tracker。.agents/skills是 base harness 的 repo-local workflow 层。
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.
- 4d ago First seen · 44 lines · 559 tokens per session scan A 791d965ba002
harness is a cursor rule published in the GitHub repository SisyphusSQ/harness-template (11 stars, last pushed 12d ago), licensed MIT. It adds 559 tokens to every session, about $0.0028 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.