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/hermeticormus/linux-sysadmin-skills/sysadmin-diagnosenpx skills add HermeticOrmus/linux-sysadmin-skills --skill sysadmin-diagnosegit clone --depth 1 https://github.com/HermeticOrmus/linux-sysadmin-skillsWrote 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/hermeticormus/linux-sysadmin-skills/sysadmin-diagnose)<a href="https://agentmods.dev/skills/hermeticormus/linux-sysadmin-skills/sysadmin-diagnose"><img src="https://agentmods.dev/badge/skills/hermeticormus/linux-sysadmin-skills/sysadmin-diagnose.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 | $0.00063 | $0.00330 |
| Opus 5 | $0.00032 | $0.00165 |
| Sonnet 5 | $0.00013 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
sysadmin-diagnose 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 3d 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
System diagnosis
A system issue is happening. Diagnose and fix it on a Debian/Ubuntu Linux machine using a systematic, hypothesis-driven loop. Gather evidence before changing anything; confirm before applying a fix.
Diagnostic steps
- Describe the problem: what is happening, and when did it start?
- Gather information:
- System logs:
journalctl -xe - Specific service logs:
systemctl status <service>andjournalctl -u <service> -xe - Resource usage:
top,htop,df -h - Network:
ip addr,ping,ss -tlnp
- System logs:
- Identify patterns: is it consistent or intermittent?
- Check recent changes: what changed before the issue appeared?
- Research: look for known issues.
- Test hypotheses: verify the likely cause before acting.
- Implement the fix: apply the solution.
- Verify: confirm the issue is resolved (
systemctl is-active <service>, reproduce the original symptom).
Be systematic and thorough. Form a hypothesis from the evidence rather than guessing, and document findings for future reference.
See full content at https://github.com/HermeticOrmus/linux-sysadmin-skills.
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.
- 3d ago First seen · 31 lines · 63 tokens per session scan A da5351654151
sysadmin-diagnose is a skill published in the GitHub repository HermeticOrmus/linux-sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 330 once invoked, about $0.0003 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-31.
Other skills, from other repositories
system-admin
Linux system administration and monitoring.
vps-cleanup
Systematic VPS cleanup — analyze files, categorize by importance, safely delete temporary/old data to free disk space.
alert-rule-troubleshoot
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…
ops-troubleshooting
This skill should be used when the user asks to "troubleshoot", "diagnose", "debug alert", "investigate incident", "locate a fault", "investigate an alert", "diagnose a problem", "fix an issue", "check alerts", "analyze alerts", "root cause analysis", "check metrics", "check logs", or discusses…
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
promql-generator
Generate PromQL queries from natural language.