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/xiaolai/vmark/plan-auditnpx skills add xiaolai/vmark --skill plan-auditgit clone --depth 1 https://github.com/xiaolai/vmarkWhat 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.00042 | $0.00508 |
| Opus 5 | $0.00021 | $0.00254 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
plan-audit 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.
What it actually says
Plan Audit
Overview
Audits completed work against a plan (WIs + acceptance + tests) and reports gaps, logic errors, and missing coverage with file/line references.
Workflow (Audit)
-
Locate the plan
- Prefer
dev-docs/plans/<plan>.md. - If unclear, ask for the plan path or the WI list.
- Prefer
-
Extract audit checklist
- For each WI, list:
- Goal
- Acceptance criteria
- Tests required
- Touched areas (files/symbols)
- For each WI, list:
-
Map implementation to WIs
- Use
git log,git show --stat,rg, and file inspection. - Record which files/commits satisfy each WI.
- Use
-
Gap & correctness analysis
- Check each acceptance item vs actual behavior.
- Find logic errors, edge-case failures, and incomplete flows.
- Validate test coverage against the “Tests (first)” section.
- If the plan references specs, verify implementation matches those specs.
- If the plan is missing acceptance/tests, record it as a plan-quality gap.
-
Report findings
- Order by severity: Critical → High → Medium → Low.
- Each finding must include:
- WI reference
- File path + line
- Why it violates the plan
- Expected behavior per plan
Output Format (required)
- Findings (ordered by severity)
File:lineand WI reference- Impact and suggested fix
- Plan Gaps Summary
- WI‑### → missing/partial acceptance items
- Test Coverage Gaps
- Missing tests, broken tests, or “test not written”
- Notes / Risks
- Any assumptions or unverified areas
- Evidence
- Cite concrete evidence for each finding (files/lines/commit IDs).
Audit Rules
- Do not run tests here unless the user explicitly asks; this is an inspection pass.
- Be strict about spec drift: if behavior diverges from plan text, flag it.
- If you cannot locate the plan, stop and ask for it.
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 · 63 lines · 42 tokens per session scan A a13695e438e2
plan-audit is a skill published in the GitHub repository xiaolai/vmark (544 stars, last pushed 2d ago), licensed ISC. It adds 42 tokens to every session and 508 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.