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-featurenpx skills add Joe-rq/harness-lab --skill source-command-featuregit 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-feature)<a href="https://agentmods.dev/skills/joe-rq/harness-lab/source-command-feature"><img src="https://agentmods.dev/badge/skills/joe-rq/harness-lab/source-command-feature.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.00022 | $0.00589 |
| Opus 5 | $0.00011 | $0.00295 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
source-command-feature 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
source-command-feature
Use this skill when the user asks to run the migrated source command feature.
Command Template
/feature
目标
引导用户创建 feature 型 REQ。
前置检查
- 确认
requirements/目录存在。不存在 → 提示先运行/harness-setup - 确认
package.json中有req:create脚本。不存在 → 提示先运行/harness-setup - 运行
npm run req:status确认当前 worktree 无活跃 REQ。有活跃 REQ → 提示先完成或搁置当前 worktree 的 REQ；如需并行新开一条线，改用source-command-worktree-req - 如需查看全局并行状态，运行
npm run req:status -- --all
执行步骤
Step 1: 收集功能信息
使用 AskUserQuestion 询问：
- 功能名称（必填）：简短描述要实现的功能，如"用户邮箱验证"
- 用户痛点（必填）：用户当前遇到什么问题？
- 业务背景（可选）：为什么现在要做？
Step 2: 创建 feature REQ
运行：
npm run req:create -- --title "feat: [功能名称]" --type feature
Step 3: 补充功能详情
用 Edit 将 REQ 中的占位符替换为用户提供的实际信息：
[请描述]（背景-用户痛点）→ 用户的痛点[请描述]（背景-业务背景）→ 用户的业务背景[功能名称]（目标）→ 用户的实际功能名称
Step 4: 提示用户确认
重点提醒：
- Scope Control 的 CAN/CANNOT 必须填写（feature 型最易功能蔓延）
- 考虑是否需要创建设计文档（
docs/plans/{reqId}-design.md） - 补充"颗粒度自检"
- 确认后运行
npm run req:start -- --id {reqId} --phase implementation
输出
- 创建的 REQ ID 和文件路径
- REQ 类型：feature
- 已预填充：用户痛点/业务背景占位、Scope Control 必填提示、建议创建设计文档
- 下一步：补充 Scope Control CAN/CANNOT，运行
req:start
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 · 64 lines · 22 tokens per session scan A c360bf4d1073
source-command-feature is a skill published in the GitHub repository Joe-rq/harness-lab (20 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 589 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…