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 skills add kanfu-panda/pdlc-skills --skill pdlc-shipgit clone --depth 1 https://github.com/kanfu-panda/pdlc-skillsWrote 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/kanfu-panda/pdlc-skills/pdlc-ship)<a href="https://agentmods.dev/skills/kanfu-panda/pdlc-skills/pdlc-ship"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-ship/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/kanfu-panda/pdlc-skills/pdlc-ship"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Tool Misuse · line 4 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 64 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Prompt Injection · line 22 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 22 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00030 | $0.09578 |
| Opus 5.5 | $0.00012 | $0.03831 |
| Sonnet 5.5 | $0.00006 | $0.01916 |
| Haiku 4.5 | $0.00003 | $0.00958 |
Grade A, and why
pdlc-ship 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 14d 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
发布工作流
串联发布一个版本所需的所有步骤:收评审通过的功能 → 跑测试 → 升级 VERSION → 更新 CHANGELOG → 写发布说明草稿 → 创建 tag。CI 配置默认不动(见 §1.6)。
⛔ IRON LAW · 不可违反的硬门禁
以下规则为不可协商的执行约束:
- 文件必须落盘:所有带编号(功能ID / 缺陷ID)的文档,必须作为实际文件写入磁盘,不可仅在对话中输出。
- 阶段必须落章:每个阶段完成后必须在状态机
docs/.pdlc-state/<feature-id>.json追加 history,不可跳过。 - 测试必须存在:进入
/pdlc-implement前,对应测试必须存在且处于红灯状态。违反则中止。 - 自检必须执行:段二自检为强制步骤,不得以"已经很好了"为由跳过。
- 防循环:段三修复为单次,不递归。无法自动修复的问题记录到报告,继续往下走。
- 状态必推进:成功执行某 phase 后
current_stage必须变更。收尾时若发现current_stage未推进,视为失败并报错,不得静默返回(防止外层循环拿滞后的状态空转烧额度)。唯一例外:命中人工点主动 block 时,current_stage保持不变但必须写last_phase_result.ok=false+blocked_reason。
违反任一条 = 立即中止当前命令,输出违规详情,等待人工介入。
⛔ 发布是破坏性·不可逆操作:打 tag / bump 版本 / 触发 CI/CD 属破坏性范畴。
--autonomous对本命令无效——即使带该参数,§1.1(未完成功能)与 §1.2(测试门)的人工确认仍必须真实由人应答。自主循环(/pdlc-loop-run)停在「评审通过、next_step为pdlc-ship」(循环文档里称review_done),永不进入本命令。
段一:执行
参数带
--tag-after-merge:只做「合并后补打」(见 1.5 末尾),跳过下面全部步骤。
1.1 前置检查
- 确认当前分支不是
master/main(参考 CLAUDE.md §5) - 确认工作区干净(
git statusclean) - 盘点
docs/.pdlc-state/下的功能(跳过_前缀的索引文件与statusline.json),逐个归入四类:- 可发布:
next_step为pdlc-ship,且last_phase_result.ok不是false——评审(或功能编排)已通过、等着发布。这一类纳入本次发布 - 已发布:
current_stage为ship_done或deploy_done——上一次发布已纳入,本次不再收 - 旧版终态写法:
current_stage以_done结尾但不是上面两个(如feature_done/fix_done/review_done)——旧版本写入,分不清是「已发布」还是「评审通过、待发布」。逐个列出,请人确认归入可发布还是已发布;--autonomous也不替人判 - 进行中:其余全部(含
last_phase_result.ok为false的阻塞功能) - 有进行中的功能 → 列出来并询问是否继续(用户明确同意才继续;进行中的功能不纳入本次发布)
- 可发布为空 → 告知「没有评审通过、待发布的功能」,询问是否仍要发布(如只发文档 / 依赖升级)
- 可发布:
- 质量闸门检查(若项目有
docs/00_standards/quality-targets.yml): 读docs/07_reviews/quality/下最近一份.md报告(同名.html只是视图, 闸门一律以.md为准——两者若不一致,信.md):- 无任何报告 → 提示先跑
/pdlc-quality,询问是继续还是先出报告 - 报告总判定未达标 → 默认不放行;要发必须由人显式 override 并写明理由, 该理由需记入本次发布的 CHANGELOG 或发布说明(不允许无声跳过)
- 报告过期——分两档处理,不是所有过期都等价(见下)
- 达标且未过期 → 在发布报告里引用该报告路径、日期与 commit SHA 作为质量证据
- 无任何报告 → 提示先跑
What ships with it
4 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.
- 14d ago Changed · +44 lines · +30 tokens per session d8695d221cc7
- 19d ago Changed · +34 lines 18de020a0282
- 20d ago Changed · +4 lines e3e24a5ffe03
- 1mo ago Changed · +214 lines 53596915fd0e
- 1mo ago Changed · +29 lines 1611802a7f98
- 1mo ago First seen · 159 lines · 0 tokens per session scan A b47e683eceba
pdlc-ship is a skill published in the GitHub repository kanfu-panda/pdlc-skills (18 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 9,578 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-31.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
gitlab-workflow
GitLab best practices for merge requests, CI/CD pipelines, issue tracking, and DevOps workflows.
gitflow
Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release or hotfix, writing a commit message, or setting up branch…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release
Cut a booping plugin release — verify the version bump against the last published tag, draft public-voiced release notes, merge the release branch into master, tag, and publish the GitHub release. Use when cutting a vX.Y.Z release of this repo.