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-relategit 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-relate)<a href="https://agentmods.dev/skills/kanfu-panda/pdlc-skills/pdlc-relate"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-relate/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-relate"><img src="https://agentmods.dev/badge/skills/kanfu-panda/pdlc-skills/pdlc-relate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Prompt Injection · line 18 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.00023 | $0.02001 |
| Opus 5 | $0.00012 | $0.01001 |
| Sonnet 5 | $0.00005 | $0.00400 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
pdlc-relate 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 today.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature 关系链管理
管理 PDLC feature 之间的关系链。维护反向索引 docs/.pdlc-state/_relations.json 和全局图 docs/.pdlc-state/_graph.md。
段一：执行子命令
从 $ARGUMENTS 解析子命令。子命令分两类，只读类绝不写任何文件：
| 类别 | 子命令 | 写什么 |
|---|---|---|
| 写入类 | set / rebuild |
<fid>.json 的 relations 块（仅 set）、_relations.json、_graph.md |
| 只读类 | query / impact / orphans / validate |
不写 |
只读类遇到 _relations.json 缺失或比任一状态文件旧时：从各状态文件的 relations 块当场现算（只在内存里），
并在输出里注明「索引缺失 / 已过期，本次现算、未落盘；要持久化请跑 /pdlc-relate rebuild」。
不要替用户顺手 rebuild——查询命令悄悄改仓库，用户会在 git status 里看到两个来路不明的文件。
set <fid> <type> <target-fid> [target-fid...]
为 feature <fid> 添加 <type> 关系，指向一或多个目标。
- 读
docs/.pdlc-state/<fid>.json；若无relations块（旧状态文件 / Phase 1 关系块可选），先初始化六类空块（extends/depends_on/supersedes/resolves/conflicts_with/relates_to），再在relations.<type>数组追加目标（去重）relations存在但不是六键对象（体检报relations-not-object，如数组形态）→ 停下，不写。 把现有条目原样列出，请人确认迁移方式后再动。直接初始化六类空块会把原有条目连同其中的说明文字 一起覆盖掉——这是静默的数据丢失，比关系写不进去更坏
- 若
<type>是对称类型（conflicts_with / relates_to）→ 同时在每个目标的<fid>.json镜像写入 - 写回后调用本命令
rebuild流程刷新_relations.json+_graph.md
query <fid>
显示 <fid> 的全部关系（出边 + 从 _relations.json 读入边）。
impact <fid> ⭐ 杀手锏
分析改动 <fid> 的影响半径。读 _relations.json（缺失或过期时按上文现算，不落盘）：
- 🔴 直接影响（depth 1 入边）：只有 extends / depends_on 本 feature 的，必须协调
- 🟡 间接影响（depth ≥2 传递入边）：沿 extends / depends_on 传递的，应 review
- 🟢 历史（指向已抵达终态——
current_stage以_done结尾——的 feature 的边 / resolves 的缺陷）：仅审计 relates_to/conflicts_with是弱关系与互斥，不进 🔴 / 🟡，单列「相关 / 冲突」- 体检中不入图的关系（数组形态、表外类型、散文目标）不要解读成 feature 依赖——原样列在体检块里，交给人判断 输出树状结构 + 建议（先 review 哪些 PRD / 是否该新建 supersedes feature 而非就地改）。
orphans
列出 _relations.json 中 inbound + outbound 均为空的 feature（可能是孤立 / 死代码候选）。
rebuild
扫描所有 docs/.pdlc-state/<id>.json 的 relations 块 + 文档追溯头的 关系: 行，重建：
_relations.json：nodes（id→name/stage/terminal）+ edges（flat 有向列表）+ index（每节点预计算 inbound/outbound）terminal=current_stage以_done结尾（见上方「判终态的唯一依据」）。不读terminal_state—— 它是目标不是事实，拿它算会把「停在 review、目标写着 review_done」的 feature 标成已完成- 只收六键对象形态、目标为合法 feature ID 的关系；体检报
relations-not-object/relations-unknown-type/relations-target-not-id的不入图，列进输出的体检块 - 目标 ID 没有状态文件（
relations-dangling）的不入 edges，交给validate报告——不要为了过自检去造占位节点
_graph.md：mermaid 图，边样式按类型区分（supersedes 虚线 / conflicts_with 粗线 / 其余实线），顶部加<!-- AUTO-GENERATED by /pdlc-relate · do not edit by hand -->
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.
- today Changed · +34 lines ea8181258601
- 12d ago First seen · 92 lines · 23 tokens per session scan A 9de61fca7b23
pdlc-relate is a skill published in the GitHub repository kanfu-panda/pdlc-skills (13 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,001 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
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
find-hypertable-candidates
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…