Borrowing it
Nothing to install: this file belongs to Joe-rq/harness-lab. 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/Joe-rq/harness-lab/master/.agents/skills/source-command-harness-setup/SKILL.mdgit clone --depth 1 https://github.com/Joe-rq/harness-labWrote 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/joe-rq/harness-lab/source-command-harness-setup)<a href="https://agentmods.dev/skills/joe-rq/harness-lab/source-command-harness-setup"><img src="https://agentmods.dev/badge/skills/joe-rq/harness-lab/source-command-harness-setup/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/joe-rq/harness-lab/source-command-harness-setup"><img src="https://agentmods.dev/badge/skills/joe-rq/harness-lab/source-command-harness-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01746 |
| Opus 5.5 | $0.00022 | $0.00698 |
| Sonnet 5.5 | $0.00011 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
source-command-harness-setup 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 1mo 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-harness-setup
Use this skill when the user asks to run the migrated source command harness-setup.
Command Template
/harness-setup
目标
将 harness-lab 治理框架接入到当前 Git 项目，并让安装结果与当前仓库的真实治理契约一致。
前置检查
-
Git 仓库检测
- 当前目录必须包含
.git/ - 如果不是 Git 仓库，先提示用户运行
git init
- 当前目录必须包含
-
现有治理文件检测
- 检查是否存在：
AGENTS.md,CLAUDE.md,requirements/,.claude/progress.txt - 如果存在，记录冲突文件列表
- 当前安装器的真实策略是默认跳过已有文件，避免覆盖目标项目内容
- 检查是否存在：
推荐执行方式
在目标项目中运行：
node /path/to/harness-lab/scripts/harness-install.mjs --defaults
node /path/to/harness-lab/scripts/harness-install.mjs --defaults --dry-run
如果目标项目的 package.json 在子目录（例如 app/package.json），仍在 Git 根目录运行安装器，并显式指定脚本绑定位置：
node /path/to/harness-lab/scripts/harness-install.mjs --defaults --package-dir app
包含治理 hooks：
node /path/to/harness-lab/scripts/harness-install.mjs --defaults --with-hook
如果 harness-lab 以本地 tarball 分发，package.json 暴露 harness-install bin，可用（npm pack 打印的文件名为准）：
npm pack
npm exec --yes --package=./harness-lab-<version>.tgz -- harness-install --defaults
npm exec --yes --package=./harness-lab-<version>.tgz -- harness-install --defaults --dry-run
npm exec --yes --package=./harness-lab-<version>.tgz -- harness-install --defaults --with-hook
本仓库不发布到公开 registry，因此没有 npx --package=harness-lab 这类可用入口。
模块
核心模块（必须安装）：
AGENTS.md- 治理规则主入口CLAUDE.md- 会话入口协议requirements/- REQ 生命周期管理.claude/progress.txt- 跨会话进度交接
默认模块：
| 模块 | 说明 | 默认 |
|---|---|---|
docs/ |
设计稿和规范目录 | yes |
context/ |
业务/技术/经验索引 | yes |
skills/ 与 .agents/skills/source-command-* |
阶段导航技能、Claude Code source-command skills（含 worktree-req） |
yes |
| CLI 脚本 | REQ lifecycle/status/experience、reflect/align、audit/health、docs gate、doctor、invariant 与其运行依赖 | yes |
| 治理 hooks | .claude/settings.example.json, scripts/session-start.js, scripts/req-check.js, scripts/scope-guard.mjs, 本地 hook 配置 |
no，需 --with-hook |
安装器真实行为
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.
- 1mo ago Changed · +2 lines b22e932f4e46
- 2mo ago First seen · 146 lines · 56 tokens per session scan A 1699d7e082dd
source-command-harness-setup is a skill published in the GitHub repository Joe-rq/harness-lab (23 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,746 once invoked, about $0.0002 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.