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 agentmods add skills/yunyoujun/advjs/adv-debugnpx skills add YunYouJun/advjs --skill adv-debuggit clone --depth 1 https://github.com/YunYouJun/advjsWhat 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 | $0.00051 | $0.01955 |
| Opus 5 | $0.00026 | $0.00978 |
| Sonnet 5 | $0.00010 | $0.00391 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
adv-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 2d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADV Debug Skill
You are a visual novel project debugger and analyzer for ADV.JS. You systematically examine projects for structural issues, dead paths, inconsistencies, and coverage gaps.
Overview
ADV.JS projects can grow complex with multiple chapters, branching narratives, and interconnected characters. This skill helps identify issues before they reach players.
Workflow
Step 1: Run Validation
adv check
Collect the validation results: syntax errors, unresolved character references, missing scene definitions.
If the only issues are unresolved character / scene refs and you want stubs auto-generated:
adv check --fix
--fix creates .character.md / scenes/*.md stub files for every unresolved reference. Existing files are never overwritten. Syntax errors and location issues are not auto-fixed — those need human attention.
Step 2: Load Full Context
adv context --full
Read the full project context to understand:
- World setting and rules
- Story structure and chapter outline
- Character roster and relationships
- Scene inventory
Step 3: Analyze Branch Structure
For each chapter, generate a branch graph from the AST — don't eyeball the .adv.md. The CLI exposes three formats:
# Default — mermaid flowchart (embed in reports)
adv debug branches adv/chapters/chapter_01.adv.md
# Structured graph (drive automated path traversal)
adv debug branches adv/chapters/chapter_01.adv.md --format=json
# Indented outline (terminal-friendly)
adv debug branches adv/chapters/chapter_01.adv.md --format=text
The JSON shape is:
{
"nodes": [
{ "id": "start", "kind": "start", "label": "START" },
{ "id": "scene_3", "kind": "scene", "label": "学校", "astIndex": 3 },
{ "id": "choices_42", "kind": "choices", "label": "Choice (2 options)", "astIndex": 42 },
{ "id": "choices_42_opt1", "kind": "option", "label": "好的，麻烦你了" },
{ "id": "end", "kind": "end", "label": "END" }
],
"edges": [{ "from": "start", "to": "scene_3" }],
"deadOptions": 0,
"sceneCount": 5
}
What ships with it
1 file 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.
- 2d ago First seen · 234 lines · 51 tokens per session scan A bd53aa834750
adv-debug is a skill published in the GitHub repository YunYouJun/advjs (324 stars, last pushed 13d ago), licensed MPL-2.0. It adds 51 tokens to every session and 1,955 once invoked, about $0.0003 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-30.
Other skills, from other repositories
anti-cheat-systems
Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs. Use this skill when analyzing EAC, BattlEye, Vanguard, FACEIT AC, kernel callbacks, handle protection, manual-map detection, boot-start drivers, BYOVD, DMA threats, or behavioral telemetry in game security research.
windows-kernel-security
Guide for Windows kernel internals and security mechanisms used in game protection and low-level research. Use this skill when working with drivers, IRQL-sensitive callbacks, EPROCESS, ETHREAD, MMVAD internals, IOCTL paths, DSE, PatchGuard, HVCI, PiDDBCache, MmUnloadedDrivers, or kernel memory inspection.
game-hacking-techniques
Guide for game-hacking technique taxonomy and threat modeling relevant to game security. Use this skill when researching memory access, code injection, overlays, input simulation, engine-specific attack surfaces, or how modern anti-cheat systems constrain user-mode, kernel-mode, hypervisor, and DMA-based cheat…
graphics-api-hooking
Guide for graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan. Use this skill when working with Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, or graphics debugging in game security research.
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
awesome-game-security-overview
Guide for understanding and contributing to the awesome-game-security curated resource list. Use this skill when adding new resources, organizing categories, mapping topics across anti-cheat, Windows kernel, DMA, reverse engineering, and game-engine research, or maintaining README.md format consistency.