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/badwally/theknowledge/wiki-finalize-draftsnpx skills add badwally/TheKnowledge --skill wiki-finalize-draftsgit clone --depth 1 https://github.com/badwally/TheKnowledgeWhat 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.00023 | $0.00460 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
wiki-finalize-drafts 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
What This Does
Surfaces stale draft pages, identifies what's blocking finalization (missing
citations, failing validator), fixes the blockers, and runs wiki finalize.
Reference conventions: WIKI.md § 8 (draft lifecycle), § 12.2 lint check stale-drafts.
Usage
/wiki-finalize-drafts # Review all stale drafts
/wiki-finalize-drafts wiki/synthesis/foo.md # Target one page
Execution Steps
-
Find drafts: Run
wiki lint --scope stale-draftsto list pages withdraft: trueolder than 7 days. -
Prioritize: For each draft, classify:
- Cat A — has
## Sources citedsection with[[sources/...]]links → ready to finalize - Cat B — has claims but no citations → needs cite-suggest
- Cat C — stub content → flag for user decision (finalize or abandon)
- Cat A — has
-
Cat A — finalize directly:
.venv/bin/wiki finalize wiki/<type>/<slug>.md -
Cat B — add citations first: Run
/wiki-cite wiki/<type>/<slug>.md(or usewiki cite-add) to surface citation candidates. Then finalize. -
Cat C — present to user: Show the slug and ask: finalize as-is, abandon, or skip? To abandon:
.venv/bin/wiki finalize wiki/<type>/<slug>.md --abandon -
Report: State how many pages were finalized, abandoned, skipped.
Key constraints
- Never modify page body via direct Edit for citation purposes — use
wiki citeorwiki cite-add. wiki finalizewill fail if citation grounding is not met; fix citations, don't force.draft: truein frontmatter is the only authoritative source of draft status.
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 · 50 lines · 23 tokens per session scan A 50d4abb9f27e
wiki-finalize-drafts is a skill published in the GitHub repository badwally/TheKnowledge (23 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 460 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-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.