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-changeloggit 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-changelog)<a href="https://agentmods.dev/skills/kanfu-panda/pdlc-skills/pdlc-changelog"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-changelog/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-changelog"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.00381 |
| Opus 5 | $0.00005 | $0.00191 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
pdlc-changelog 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 12d 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
更新变更日志
根据最近的 git 提交记录，更新指定服务或应用的 CHANGELOG.md。
工作流程
- 运行
git log查看最近的提交记录 - 按约定式提交分类：feat / fix / docs / chore / refactor / test
- 更新对应服务/应用的
CHANGELOG.md，使用templates/changelog-template.md作为格式与分节模板 - 遵循 Keep a Changelog 格式
分类规则
- 新增（Added）: feat 类型的提交
- 修复（Fixed）: fix 类型的提交
- 变更（Changed）: refactor 类型的提交
- 移除（Removed）: 删除功能相关的提交
- 文档（Docs）: docs 类型的提交
要求
- 每条记录简洁明了，描述"做了什么"和"为什么"
- 如果涉及破坏性变更，需特别标注
目标: $ARGUMENTS
本命令的 handoff 输出：
✅ 变更日志 完成
📦 产出：CHANGELOG.md
👉 下一步：（本次流程结束，无后续）
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.
- 12d ago First seen · 50 lines · 10 tokens per session scan A d6e37b75198c
pdlc-changelog is a skill published in the GitHub repository kanfu-panda/pdlc-skills (13 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 381 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-31.
Other skills, from other repositories
log-changes
Use when asked to update the changelog, document version changes, prepare a release, or add entries for recent work, and when reviewing a diff or pull request that touches CHANGELOG.md. Produces concise user-facing CHANGELOG.md entries, follows Keep a Changelog and Semantic Versioning, and verifies that new bullets…
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.
changelog
Generate CHANGES entries from branch commits and PR context.
releasing
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness.
changelog-rewrite-aggressively
Rebase out the branch's earlier changelog commits and regenerate its entries fresh; commits only with --commit.
release-update-downstream-packages
Use when rolling a newly published package release through every maintained consumer repository and verifying CI.