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/sd0xdev/sd0x-harness/create-prnpx skills add sd0xdev/sd0x-harness --skill create-prgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWhat 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.00124 | $0.10825 |
| Opus 5 | $0.00062 | $0.05412 |
| Sonnet 5 | $0.00025 | $0.02165 |
| Haiku 4.5 | $0.00012 | $0.01082 |
Grade C, and why
create-pr scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| How the path is carried | Run `mktemp -d` **once**, read the path it prints, and substitute that **literal absolute path** into every later command. Each Bash invocation is a fresh shell, so `DIR=$(mktemp -d)` followed How it starts
The opening of the file, as written. The whole thing — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Input
/create-pr [--head <branch>] [--base <branch>] [--title <title>] [--stack <branch...>] [--update] [--execute] [--dry-run]
--head: Source branch (default: current branch)--base: Target branch (default:{TARGET_BRANCH}ormain)--title: Override auto-generated title (rejected with--stack)--stack: Stacked PR chain mode, bottom layer first (mutually exclusive with--head; the bottom layer's base follows the same--base/{TARGET_BRANCH}/mainresolution as normal mode) — see Stacked PR Mode--update: Force update mode (re-generate title/body for existing PR)--dry-run: Show command without executing (default). Scopes to mutatingghcalls — the Step 1git fetch --prune originstill runs, so the preview reflects the server's real refs--execute: Actually create/update the PR (requires user confirmation)- No args: use current branch → default target, dry-run mode. Auto-detects existing PR → update mode
Workflow
0. Mode Dispatch (first, before anything else)
When --stack is present: read references/stack-mode.md and run Phases A–D from there. Skip generic Steps 1, 5, 6 and 7 entirely — Phase A must run git fetch --prune origin and classify sync state before any PR planning, so the generic ls-remote / local base..head path must not run first. What is reused, per layer, exactly as Phase C directs:
| Reused | Skipped |
|---|---|
| Steps 2–4 content generation (ticket ID, title, body) | Step 1 gather — Phase A replaces it |
| Step 4b sanitization, Step 7b post-creation verify | Step 5 pre-flight + mode detection — Phase A/B replace it |
| Step 5a's smart-diff update logic — the routing decision is Phase B's, the diff-and-update mechanics are Step 5a's | Steps 6–7 single-PR output/execute — Phase C emits per-layer commands instead |
Otherwise continue with Step 1 below.
1. Gather Info
The fetch runs first and alone — the ref-range reads below it (git log and git diff
over refs/remotes/origin/*) depend on the remote-tracking refs it refreshes, so it cannot
join the parallel batch. It runs even in --dry-run (the dry-run promise at the top scopes to
mutating gh calls; refreshing and pruning local remote-tracking refs is how the preview
describes the commits that would actually ship). ls-remote in the next fence only LISTS the
server's refs — it never updates refs/remotes/* — so without this fetch they can be missing
or stale (another clone pushed, or this one never fetched) and the PR body would describe old
commits. Same exact form and same discipline as stack mode's Phase A: the explicit exit keeps
a failed fetch from being followed by reads of stale refs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 510 lines · 124 tokens per session scan C 57c5c2187428
create-pr is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 10,825 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
make-skill
Use this skill when sedimenting a session into a reusable workspace skill. Triggers when the user wants to turn the current conversation, workflow, or troubleshooting path into a SKILL.md. Phrases like 'turn this into a skill', 'remember how I did X', 'save this workflow', 'make a skill from this', and any /make-skill…
make-skill
用于把当前会话沉淀为可复用的 workspace skill。当用户希望把当前对话、工作流或排错路径写成 SKILL.md 时触发。触发表达包括「把这个变成 skill」「记住我是怎么做 X 的」「保存这个工作流」「make a skill from this」以及任何 /make-skill 调用。.
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
docx
当用户需要创建、读取、编辑或处理 Word 文档（.docx）时，使用此技能。触发场景包括提到“Word 文档”、“.docx”，或要求生成带目录、标题、页码、信头等格式的专业文档；也包括提取或重组 .docx 内容、插入或替换图片、在 Word 文件中查找替换、处理修订或批注，以及将内容整理为正式 Word 文档。如果用户要求生成“报告”“备忘录”“信函”“模板”等 Word / .docx 交付物，也应使用此技能。不要用于 PDF、电子表格、Google Docs，或与文档生成无关的一般编程任务。.
multi_agent_collaboration
当需要其他 agent 的专长、上下文或协作支持，或用户明确要求调用其他 agent 时，使用本 skill。先查询可用 agents，再用 qwenpaw agents chat 进行双向沟通。.