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-performancenpx skills add HermeticOrmus/linux-sysadmin-skills --skill sysadmin-performancegit clone --depth 1 https://github.com/HermeticOrmus/linux-sysadmin-skillsWhat 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.00056 | $0.00620 |
| Opus 5 | $0.00028 | $0.00310 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
sysadmin-performance 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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System performance analysis
Analyze and optimize performance on a Debian/Ubuntu Linux machine. Measure before forming an opinion; tune the bottleneck, not a guess. Confirm before any change that alters kernel parameters, kills processes, or disables services.
Performance analysis steps
1. Current-state assessment
CPU:
top -bn1 | head -20
mpstat 1 5
Look at usage patterns, per-process CPU, and load average.
Memory:
free -h
vmstat 1 5
Look at RAM usage, swap usage, and memory pressure.
Disk:
df -h
iostat -x 1 5
Look at free space, I/O performance, and per-disk utilization.
Network:
ifstat 1 5
netstat -s
Look at throughput, packet statistics, and errors or drops.
Processes:
ps aux --sort=-%mem | head -10
ps aux --sort=-%cpu | head -10
Look for resource hogs, zombie processes, and process states.
2. Identify the bottleneck
Common bottlenecks: CPU saturation, memory exhaustion, disk I/O wait, network congestion, process limits. Name which one the measurements point to before tuning.
3. Optimization strategies
For CPU: identify CPU-intensive processes, check for runaway processes, consider nice/renice, review cron jobs, optimize application code.
For memory: check for leaks, review swap usage, adjust swappiness, kill memory hogs, add RAM if genuinely needed.
For disk: check usage, clean up old files, tune the I/O scheduler, consider an SSD, check for a failing disk with smartctl.
For network: check bandwidth, review firewall rules, tune network settings, check for attacks.
4. System tuning
Kernel parameters in /etc/sysctl.conf: vm.swappiness, fs.file-max, net.core parameters.
Service optimization: disable unused services, tune service configs, review startup items.
Resource limits in /etc/security/limits.conf: open-file limits, process limits, memory limits.
5. Monitoring setup
Set up ongoing monitoring: htop for a real-time view, logging for historical data, alerts for issues, and recorded performance baselines.
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.
- 2d ago First seen · 95 lines · 56 tokens per session scan A 342cab63ef1f
sysadmin-performance is a skill published in the GitHub repository HermeticOrmus/linux-sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 620 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…
host-onboard-diagnose
Diagnose onboarding failures where "categraf is installed/running but the host does not show up in the Nightingale host list, or shows unknown / has no metrics". Triggers when the user asks "why doesn't my newly installed host appear", "all the OS values in the host list are unknown", "I installed 3 collectors via…
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.