Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sd0xdev/sd0x-harnessnpx agentmods add skills/sd0xdev/sd0x-harness/post-dev-recapWrote 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/sd0xdev/sd0x-harness/post-dev-recap)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/post-dev-recap"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/post-dev-recap/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/sd0xdev/sd0x-harness/post-dev-recap"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/post-dev-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 123 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 208 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 129 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 131 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 209 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 211 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00124 | $0.04063 |
| Opus 5 | $0.00062 | $0.02031 |
| Sonnet 5 | $0.00025 | $0.00813 |
| Haiku 4.5 | $0.00012 | $0.00406 |
Grade A, and why
post-dev-recap 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/post-dev-recap — Guided Post-Development Recap
Trigger
- Keywords: post-dev-recap, 開發後導覽, walkthrough after dev, recap workflow, 本輪回顧
When NOT to Use
| Scenario | Alternative |
|---|---|
| Only need a doc (no Q&A) | /recap-doc — emits the recap markdown and stops |
| Have an existing recap, want to ask questions | /recap-ask --context <path> |
| Share-out for other developers (not the author) | /tech-brief — focuses on knowledge transfer to strangers |
| First-principles reasoning of an existing doc | /fp-brief — explains why decisions hold |
| General project Q&A, no recent change | /ask — reopens the whole repo as context |
| Deep code tracing across modules | /code-explore — execution-path walker |
Positioning vs /ask, /tech-brief, /fp-brief, /code-explore (AS-5)
| Dimension | /post-dev-recap |
/ask |
/tech-brief |
/fp-brief |
/code-explore |
|---|---|---|---|---|---|
| Trigger | Right after AI/Codex finishes a feature | Any quick question | Share-out for teammates | Explain an existing doc | Diagnose unknown code |
| Input | ScopeReport (detected live) | Free-form question | A finished feature | A document | A code question |
| Output | Recap doc + Q&A session | Answer | Brief artifact | First-principles chain | Execution-path report |
| Bounded? | Yes — scope of the just-done change | No — whole repo | No — whole feature | Document-scoped | Free search |
Command Signature
/post-dev-recap [<focus>] [--interactive] [--depth brief|normal|deep]
| Flag | Default | Description |
|---|---|---|
<focus> |
"" |
Natural-language keyword to bias section emphasis, passed to /recap-doc --focus |
--interactive |
false | Enable per-step AskUserQuestion — user can choose one of 4 actions between phases: 繼續 (continue) / 提問 (ask) / 跳段 (skip) / 結束 (end) |
--depth |
normal |
Recap depth — brief / normal / deep, passed to /recap-doc --depth |
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 Changed 68674e1485b6
- 6d ago First seen · 232 lines · 124 tokens per session scan A a22242e0b373
post-dev-recap is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed 4d ago), licensed MIT. It adds 124 tokens to every session and 4,063 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/update/pause/resume/delete/run, and always pass --agent-id explicitly.
cron
A procedure for creating and managing tasks that run automatically at a future time or repeat on a schedule. It uses QwenPaw's scheduling commands and requires an agent identifier.
mailbox
A guide for performing email and mailbox tasks through the QwenPaw mailbox system. It covers supported personal email providers, credentials, configuration, and the required mailbox workflow.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.