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 chaterm/terminal-skills --skill system-admingit clone --depth 1 https://github.com/chaterm/terminal-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/chaterm/terminal-skills/system-admin)<a href="https://agentmods.dev/skills/chaterm/terminal-skills/system-admin"><img src="https://agentmods.dev/badge/skills/chaterm/terminal-skills/system-admin.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
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.00008 | $0.00573 |
| Opus 5 | $0.00004 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
system-admin 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 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.
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
Linux System Administration
Overview
Core commands and best practices for Linux system administration, including system information viewing, resource monitoring, service management, etc.
System Information
Basic Information
# System version
cat /etc/os-release
uname -a
# Hostname
hostnamectl
# Uptime and load
uptime
Hardware Information
# CPU information
lscpu
cat /proc/cpuinfo
# Memory information
free -h
cat /proc/meminfo
# Disk information
lsblk
df -h
Resource Monitoring
Real-time Monitoring
# Comprehensive monitoring
top
htop
# Memory monitoring
vmstat 1
# IO monitoring
iostat -x 1
iotop
# Network monitoring
iftop
nethogs
Historical Data
# System activity report
sar -u 1 10 # CPU
sar -r 1 10 # Memory
sar -d 1 10 # Disk
Service Management
Systemd Services
# Service status
systemctl status service-name
systemctl is-active service-name
# Start/Stop services
systemctl start/stop/restart service-name
# Boot startup
systemctl enable/disable service-name
# View all services
systemctl list-units --type=service
Common Scenarios
Scenario 1: System Health Check
# Quick health check script
echo "=== System Load ===" && uptime
echo "=== Memory Usage ===" && free -h
echo "=== Disk Usage ===" && df -h
echo "=== Failed Services ===" && systemctl --failed
Scenario 2: Troubleshoot High Load
# 1. Check load
uptime
# 2. Find high CPU processes
ps aux --sort=-%cpu | head -10
# 3. Find high memory processes
ps aux --sort=-%mem | head -10
Troubleshooting
| Problem | Commands |
|---|---|
| System lag | top, vmstat 1, iostat -x 1 |
| Disk full | df -h, du -sh /*, ncdu |
| Memory shortage | free -h, ps aux --sort=-%mem |
| Service abnormal | systemctl status, journalctl -u |
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 · 121 lines · 8 tokens per session scan A e06b507ab9de
system-admin is a skill published in the GitHub repository chaterm/terminal-skills (58 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 573 once invoked, about $0.0000 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
skillci-guardrails
Use this skill whenever you create, edit, or review a Claude Skill — any SKILL.md file, or the eval cases/config next to one. Most SKILL.md files today are written or edited by an agent, not typed by hand, so this closes the loop by having the agent that just wrote the skill also author it defensively and verify it…
mle-workflow
Production ML engineering workflow — data contracts, reproducible training, evaluation gates, deployment, and monitoring. Use when building, reviewing, or hardening ML systems beyond notebooks.
c-system
Swiss Army Knife for macOS. Run m followed by a category.
example-skill
Writes a single changelog entry summarizing a code change, given a short description of what changed.
clean-skill
A skill with no lint issues, used as a starting point for the lint-on-type test.
skill-with-referenced-issue
Has a clean SKILL.md but an unsafe referenced script.