What is docs-maintenance?

A documentation-maintenance skill for ShadowDusk's DocFX website. DocFX turns Markdown source files into a published documentation site.

It helps update published docs, fix documentation, and determine where particular content belongs.

It helps keep edits in the correct source files and prevents common problems such as broken included-file links, outdated wording, and hardcoded versions.

How kaltinril/ShadowDusk configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kaltinril/ShadowDusk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kaltinril/ShadowDusk/main/.claude/skills/docs-maintenance/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/kaltinril/ShadowDusk

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kaltinril/shadowdusk/docs-maintenance/github.svg)](https://agentmods.dev/skills/kaltinril/shadowdusk/docs-maintenance)

Your own site

<a href="https://agentmods.dev/skills/kaltinril/shadowdusk/docs-maintenance"><img src="https://agentmods.dev/badge/skills/kaltinril/shadowdusk/docs-maintenance/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kaltinril/shadowdusk/docs-maintenance"><img src="https://agentmods.dev/badge/skills/kaltinril/shadowdusk/docs-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 458 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.00458
Opus 5.5	$0.00016	$0.00183
Sonnet 5.5	$0.00008	$0.00092
Haiku 4.5	$0.00004	$0.00046

Measured 1mo ago against content hash ff8e58669715, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-maintenance 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.

.claude/skills/docs-maintenance/SKILL.md · 32 lines

What it actually says

Docs Maintenance

Scope: published = the DocFX site

In scope: docfx/**/*.md + the 6 files it pulls in via [!INCLUDE]:
- docs/HOWTO-WASM-KNI.md
- docs/error-codes.md
- docs/glsl-uniform-naming.md
- docs/references/compilation-pipeline.md
- docs/test-shader-corpus.md
- samples/ShaderFiddle.Web/README.md
Edit the source file, not the docfx/ wrapper that includes it.
Out of scope, never touch: docs/research.md, plan/**. Internal only.

Hard rules

Phase numbers: drop for completed work (bookkeeping); keep for planned/future work (reader's tracking handle).
Write as if published: assume nuget.org packages exist. No time-relative framing ("not on nuget yet", "until first release") — it flips to wrong on publish. Frame source-build steps as evergreen "consuming an unreleased build".
No hardcoded versions: use floating * or reference Directory.Build.props <Version>.
Cross-links inside [!INCLUDE]'d files: use inline code paths (`docs/foo.md`), NOT markdown links — included files aren't site pages, links emit InvalidFileLink.
Present tense, current truth. History lives in plan/ only.

Verify before done

dotnet tool restore && dotnet docfx docfx.json → must be 0 warnings / 0 errors.

Audit greps (catch regressions)

Phase[ -]?\d|backlog|rung \d in published files → only allowed on planned/future items.
0\.\d\.\d hardcoded versions in published files.

Changes

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 · 32 lines · 40 tokens per session scan A ff8e58669715

Subscribe to this mod's changes

docs-maintenance is a skill published in the GitHub repository kaltinril/ShadowDusk (19 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 458 once invoked, about $0.0002 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-09-04.

Writing and docs

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

ShadowDusk: Skill for Claude Code