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/hjdhnx/drpy-node-skillnpx agentmods add skills/hjdhnx/drpy-node-skill/drpy-node-play-debugWrote 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/hjdhnx/drpy-node-skill/drpy-node-play-debug)<a href="https://agentmods.dev/skills/hjdhnx/drpy-node-skill/drpy-node-play-debug"><img src="https://agentmods.dev/badge/skills/hjdhnx/drpy-node-skill/drpy-node-play-debug/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/hjdhnx/drpy-node-skill/drpy-node-play-debug"><img src="https://agentmods.dev/badge/skills/hjdhnx/drpy-node-skill/drpy-node-play-debug.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.00121 | $0.07215 |
| Opus 5.5 | $0.00048 | $0.02886 |
| Sonnet 5.5 | $0.00024 | $0.01443 |
| Haiku 4.5 | $0.00012 | $0.00722 |
Grade A, and why
drpy-node-play-debug 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 1mo 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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ 已归档（2026-07-17）：本 skill 已被
drpy-node-coder取代。coder 融合了 4 个旧 skill（workflow/create/play-debug/repo-upload）的全部工作流，并自带scripts/cli.jsCLI 替代 drpy-node-mcp 服务——一个 skill、无需安装 MCP。本文件保留仅供历史参考，新工作请直接用 drpy-node-coder。
drpy-node Play Debug
快速索引
| 播放表现 | 优先判断 | 首选动作 |
|---|---|---|
detail 没有 vod_play_url |
不是播放问题 | 交回 workflow 修二级 |
parse:0 返回 /play/*.html |
假直链 | 改 parse:1 或提取 iframe/m3u8 |
player_* url 乱码 |
encrypt/base64/sign | 先解密再判直链/解析 |
| 浏览器可播但静态 HTML 无 m3u8 | JS 运行时生成 | Playwright network 兜底 |
| 多线路部分可播 | 按 flag/input 分派 | 不要一刀切 lazy |
执行契约
- 输入：source_name、detail ids、play_url、flag、当前 lazy 返回值或错误表现。
- 输出：播放类型判断、lazy 修复方案、play 接口验证结果。
- 停手：detail 不稳定、一级/搜索同时异常、上传/评估整源诉求出现时交回 workflow。
模式闸门：先判断是否允许写入
| 用户模式 | 允许动作 | 禁止动作 |
|---|---|---|
| 只读 / 规划 / dry-run / 不要改文件 | 读取、诊断、判断 lazy 类型、给修复方案和复测计划 | drpy_edit_file、重写 lazy、仓库上传/改标签 |
| 需要确认后再改 | 读取、诊断、输出播放诊断确认 | 未确认前禁止改 lazy |
| 明确要求执行 | 按同一 play_url + flag 修改并复测 |
detail 不稳定时不得深挖 lazy |
| 自主全流程 | detail 稳定时自动做低风险 lazy 修复、复测并回传 autonomous_next |
改 detail、强绕登录/验证码、高风险多分支重写 |
如果用户说“只判断 / 不要修改 / dry-run”，本 skill 只能输出播放诊断确认、lazy 修改建议和验证计划。
自主全流程调用约定
当 workflow/source-create 为“修到100 / 满分后上传 / 不要中途问我”调用本 skill，且已传入真实 source_name/ids/play_url/flag 并确认 detail 稳定时，本 skill 可自动执行低风险播放修复：
- 记录修改前 detail 摘要和 play 返回。
- 判断返回类型：直链 / 站外解析 / 播放页 / 特殊协议 / 假通过。
- 只修改 lazy 相关最小逻辑，不顺带改一级、二级、搜索。
- 用同一
play_url + flag复测。 - 返回
blocker_type和autonomous_next给 workflow。
必须停手的 blocker：
| blocker_type | 判定 | autonomous_next |
|---|---|---|
detail_unstable |
detail 没有稳定 vod_play_from/vod_play_url |
return_workflow |
hard_anti_bot |
验证码、强 headless 检测、DRM/WASM | stop_for_user |
missing_credentials |
播放需要 Cookie/Authorization/登录 | stop_for_user |
high_risk_change |
需要重写多条线路、删除模板 lazy、影响所有 flag | stop_for_user |
none |
低风险修复已完成并复测 | continue_evaluate |
Return Packet 必含：
source_name: ...
ids: ...
flag: ...
play_url: ...
修改前 play: {parse, jx, url}
修改后 play: {parse, jx, url} / 未修改
结论: 真实可播 / 假通过 / 需浏览器确认
blocker_type: none / detail_unstable / hard_anti_bot / missing_credentials / high_risk_change
autonomous_next: continue_evaluate / retry_lazy / return_workflow / stop_for_user
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.
- 1mo ago First seen · 567 lines · 121 tokens per session scan A dffd30c547f9
drpy-node-play-debug is a skill published in the GitHub repository hjdhnx/drpy-node-skill (58 stars, last pushed 1mo ago), licensed MIT. It adds 121 tokens to every session and 7,215 once invoked, about $0.0005 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…