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 skills/joe-rq/harness-lab/source-command-harness-setupnpx skills add Joe-rq/harness-lab --skill source-command-harness-setupgit 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.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.00056 | $0.01695 |
| Opus 5 | $0.00028 | $0.00847 |
| Sonnet 5 | $0.00011 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00169 |
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 5d 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 — 146 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 以 npm 包形式安装，package.json 暴露 harness-install bin 后，也可以使用：
npx --yes --package=harness-lab harness-install --defaults
npx --yes --package=harness-lab harness-install --defaults --dry-run
npx --yes --package=harness-lab harness-install --defaults --package-dir app
npx --yes --package=harness-lab harness-install --defaults --with-hook
模块
核心模块（必须安装）：
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 |
安装器真实行为
- 源目录
- 默认使用安装脚本所在仓库作为源目录
- 可通过
--source /path/to/harness-lab显式指定
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.
- 5d 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 (20 stars, last pushed 23d ago), licensed MIT. It adds 56 tokens to every session and 1,695 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…