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/kaltinril/shadowdusk/docs-maintenancenpx skills add kaltinril/ShadowDusk --skill docs-maintenancegit clone --depth 1 https://github.com/kaltinril/ShadowDuskWrote 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/kaltinril/shadowdusk/docs-maintenance)<a href="https://agentmods.dev/skills/kaltinril/shadowdusk/docs-maintenance"><img src="https://agentmods.dev/badge/skills/kaltinril/shadowdusk/docs-maintenance.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00020 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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 yesterday.
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
Docs Maintenance
Scope: published = the DocFX site
- In scope:
docfx/**/*.md+ the 6 files it pulls in via[!INCLUDE]:docs/HOWTO-WASM-KNI.mddocs/error-codes.mddocs/glsl-uniform-naming.mddocs/references/compilation-pipeline.mddocs/test-shader-corpus.mdsamples/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 referenceDirectory.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 emitInvalidFileLink. - 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 \din published files → only allowed on planned/future items.0\.\d\.\dhardcoded versions in published files.
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.
- yesterday First seen · 32 lines · 40 tokens per session scan A ff8e58669715
docs-maintenance is a skill published in the GitHub repository kaltinril/ShadowDusk (14 stars, last pushed 22d ago), licensed MIT. It adds 40 tokens to every session and 458 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…