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 skills add developkiko/DsktpCmndr --skill computer-health-checkgit clone --depth 1 https://github.com/developkiko/DsktpCmndrWrote 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/developkiko/dsktpcmndr/computer-health-check)<a href="https://agentmods.dev/skills/developkiko/dsktpcmndr/computer-health-check"><img src="https://agentmods.dev/badge/skills/developkiko/dsktpcmndr/computer-health-check.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.00209 | $0.02077 |
| Opus 5 | $0.00105 | $0.01038 |
| Sonnet 5 | $0.00042 | $0.00415 |
| Haiku 4.5 | $0.00021 | $0.00208 |
Grade B, and why
computer-health-check scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
default — it never needs sudo and only performs cleanups the user explicitly approves. This is a copy
97% identical to computer-health-check — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Computer Health Check
What this skill does
Give the user a fast, trustworthy picture of their computer's health and a short list of actions worth taking — the way a good technician would: look first, explain plainly, fix only with permission.
It runs entirely through Desktop Commander's local shell, gathers a batch of read-only diagnostics, scores each area, prints a concise summary in the chat, and then offers cleanup suggestions the user can approve one by one.
The safety contract (read this first)
This is the part that makes users trust the skill, so honor it strictly:
- Read-only by default. The collection phase only observes (sizes, counts, status). It changes nothing.
- Never use
sudoor elevation. DC blockssudo,shutdown,reboot,dd,mount,mkfs,diskpart, etc. for good reason. Every check below is designed to work without them. If something seems to need elevation, skip it and say so — don't try to work around the block. - Cleanups are opt-in. You may suggest cleanups freely, but only execute one after the user explicitly approves that specific action, and only show the exact command first.
- Prefer reversible, non-destructive actions. Emptying caches that regenerate, clearing a package-manager download cache, or emptying Trash are fine to offer. Deleting user documents, uninstalling apps, or editing system files are not — suggest those, let the user do them.
Workflow
Step 1 — Detect the OS
Determine the platform before doing anything else, because the commands differ.
- Quickest: read Desktop Commander's config (
get_config) and use thesystemInfo.isMacOS/isWindows/isLinuxbooleans (orplatformName) to pick the platform. - Or run
uname(macOS/Linux) — if it fails, assume Windows.
Then open the matching reference file and use its command set:
- macOS →
references/macos.md - Windows →
references/windows.md - Linux →
references/linux.md
Read only the one that matches. Each file contains a single batched collection script plus interpretation notes and cleanup commands.
What ships with it
3 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.
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.
- 7d ago First seen · 166 lines · 209 tokens per session scan B 9100fedbcb87
computer-health-check is a skill published in the GitHub repository developkiko/DsktpCmndr (0 stars, last pushed 2mo ago), licensed MIT. It adds 209 tokens to every session and 2,077 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 97% identical to computer-health-check, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.