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-bugfix/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-bugfix)<a href="https://agentmods.dev/skills/joe-rq/harness-lab/source-command-bugfix"><img src="https://agentmods.dev/badge/skills/joe-rq/harness-lab/source-command-bugfix/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-bugfix"><img src="https://agentmods.dev/badge/skills/joe-rq/harness-lab/source-command-bugfix.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00548 |
| Opus 5.5 | $0.00010 | $0.00219 |
| Sonnet 5.5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
source-command-bugfix 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 2mo 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-bugfix
Use this skill when the user asks to run the migrated source command bugfix.
Command Template
/bugfix
目标
引导用户快速创建 bugfix 型 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: 收集 Bug 信息
使用 AskUserQuestion 询问：
- Bug 简述（必填）：一句话描述 Bug 现象，如"登录页面点击提交后无响应"
- 影响范围（必填）：哪些功能/用户受影响，如"所有使用邮箱登录的用户"
Step 2: 创建 bugfix REQ
运行：
npm run req:create -- --title "fix: [Bug 简述]" --type bugfix
Step 3: 补充 Bug 详情
用 Edit 将 REQ 中的占位符替换为用户提供的实际信息：
[请描述]（背景-Bug 现象）→ 用户的 Bug 简述[请描述]（背景-影响范围）→ 用户的影响范围
Step 4: 提示用户确认
提示用户：
- 检查自动填充的内容是否符合实际情况
- 补充"颗粒度自检"
- 确认后运行
npm run req:start -- --id {reqId} --phase implementation
输出
- 创建的 REQ ID 和文件路径
- REQ 类型：bugfix
- 已预填充：Bug 特化目标、skip-design-validation、回归测试验收标准
- 下一步：补充颗粒度自检，运行
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.
- 2mo ago First seen · 61 lines · 26 tokens per session scan A 18080d2167da
source-command-bugfix is a skill published in the GitHub repository Joe-rq/harness-lab (23 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 548 once invoked, about $0.0001 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…