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/codealive-ai/ai-driven-development/maintaining-windows-healthnpx skills add CodeAlive-AI/ai-driven-development --skill maintaining-windows-healthgit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWrote 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/codealive-ai/ai-driven-development/maintaining-windows-health)<a href="https://agentmods.dev/skills/codealive-ai/ai-driven-development/maintaining-windows-health"><img src="https://agentmods.dev/badge/skills/codealive-ai/ai-driven-development/maintaining-windows-health.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.00191 | $0.03861 |
| Opus 5 | $0.00096 | $0.01930 |
| Sonnet 5 | $0.00038 | $0.00772 |
| Haiku 4.5 | $0.00019 | $0.00386 |
Grade A, and why
maintaining-windows-health 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 6d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining Windows 11 Health
Recovery and prevention playbook for Windows 11 disk and memory crises. A Windows port of the maintaining-macos-health skill: same three layers (triage → tiered recovery → automation/alerting) and the same safety invariant — scan → JSON → user picks in a UI → apply deletes only what was picked — but with Windows-native tooling and Windows-specific "never touch" rules. The same playbook works for routine cleanup or first-time setup on a new machine.
Table of contents
- When to use
- Skill layout
- Core mental model
- Standard workflows
- Safety rules (non-negotiable)
- Domain quirks captured
- Outcomes scale
When to use
Trigger on any of:
- Disk free < 20 % or user complains about being out of space
- BSOD / unexpected reboot / Kernel-Power 41 / WHEA error / a new crash dump in
C:\Windows\Minidump - "PC is slow", commit pressure high (
% Committed Bytes In Use> 85), pagefile growing - User wants to set up monitoring/alerting from scratch
- Migration to a new Windows PC → restore the same alerter
- General "clean my PC" / "audit storage" / "free space" requests
Skill layout
| File | Use for |
|---|---|
references/triage.md |
First 5 minutes — which signal fired (disk / commit-memory / BSOD-crash / "feels slow"), read-only snapshot |
references/cleanup-tiers.md |
Tiered cleanup playbook (10 tiers, low-risk → discuss-first), copy-paste-safe PowerShell blocks |
references/never-touch.md |
Categories that must not be deleted even elevated (hard-protected prefixes synced with the validator + Windows-only dangers) |
references/native-tools.md |
The safety floor: native Microsoft tooling, project-artifact purge marker→target map, the apply-script validator rules, third-party caveats |
references/alerting.md |
Full alerter design: 3 CRITICAL-only triggers, hysteresis, calibration, Task Scheduler interactive session, BurntToast + ntfy, S0ix/battery |
assets/win-health-check.ps1 |
Production PowerShell monitor (PS 5.1 compatible) |
assets/win-health-check.config.ps1 |
Default thresholds |
assets/Install-WinHealthCheck.ps1 |
Registers the scheduled task in the interactive user session; -Test / -Uninstall |
assets/Audit-WinHealth.ps1 |
Read-only preflight inventory (drives, Component Store, shadow storage, profiles, drivers, CFA, KFM, BitLocker, reparse points, dumps) |
assets/render-cleanup-plan.py |
Interactive HTML cleanup-plan UI. Renders categorised checkboxes from a JSON of scan findings, serves on 127.0.0.1:18347, opens the browser, waits for the user's selection, writes it to %TEMP%\cleanup-selection-<ts>.json. Used by Workflow A. Requires Python 3. |
assets/apply-cleanup-selection.py |
The only sanctioned way to apply a cleanup selection. Reads selected_items from a selection JSON and executes each item's command via PowerShell. Windows-rewritten validator (NTFS canonicalization, deny/allow longest-prefix, provider/UNC/ADS/8.3/chaining refusal, two-tier wrappers) + operations log. Supports --dry-run. |
assets/test_validate_command.py |
Adversarial unit tests for the validator — the safety-core gate. Runs on any OS. |
What ships with it
14 files 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.
- .gitignore 44 B
- assets/apply-cleanup-selection.py 20 KB runs code
- assets/Audit-WinHealth.ps1 7.1 KB runs code
- assets/Install-WinHealthCheck.ps1 6.6 KB runs code
- assets/render-cleanup-plan.py 45 KB runs code
- assets/test_validate_command.py 10 KB runs code
- assets/win-health-check.config.ps1 1.4 KB runs code
- assets/win-health-check.ps1 12 KB runs code
- README.md 6.2 KB
- references/alerting.md 9.4 KB
- references/cleanup-tiers.md 15 KB
- references/native-tools.md 9.4 KB
- references/never-touch.md 11 KB
- references/triage.md 8.0 KB
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.
- 6d ago First seen · 147 lines · 191 tokens per session scan A b962662c33a4
maintaining-windows-health is a skill published in the GitHub repository CodeAlive-AI/ai-driven-development (132 stars, last pushed 2d ago), licensed MIT. It adds 191 tokens to every session and 3,861 once invoked, about $0.0010 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
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
axum-idioms
Axum HTTP framework patterns — routing, extractors, middleware, state management. For Rust see rust-idioms.
nextjs-idioms
Next.js App Router, RSC, Server Actions, ISR. For React see react-idioms. For TypeScript see typescript-idioms.
react-idioms
React hooks, Suspense, Server Components, React 19 patterns. For TypeScript see typescript-idioms.
hono-idioms
Hono HTTP framework patterns — routing, middleware, Zod validation, RPC client. For TypeScript see typescript-idioms.