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 bolivian-peru/os-moda --skill system-monitorgit clone --depth 1 https://github.com/bolivian-peru/os-modaWrote 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/bolivian-peru/os-moda/system-monitor)<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/system-monitor"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/system-monitor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/system-monitor"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/system-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00474 |
| Opus 5 | $0.00021 | $0.00237 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
system-monitor 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 12d 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 Monitor Skill
You can monitor every aspect of the system in real time.
Quick Health Check
system_health()
Returns CPU usage per core, memory (total/used/available), swap, disk usage per mount, load average, and uptime.
Process Monitoring
List processes by resource usage
system_query({ query: "processes", args: { sort: "cpu", limit: 20 } })
system_query({ query: "processes", args: { sort: "memory", limit: 20 } })
Investigate a specific process
system_query({ query: "processes", args: { name: "firefox" } })
Disk Usage
system_query({ query: "disk" })
Returns per-mount: filesystem type, total/used/available space, usage percentage.
Diagnosis Workflow
When the user reports a problem:
- Check health first —
system_health()for the overview - Check memory — recall past similar issues:
memory_recall({ query: "similar problem description" }) - Drill into specifics — processes, disk, network as needed
- Correlate — "your disk is full because Docker images take 40GB"
- Store the diagnosis —
memory_store({ summary: "...", detail: "...", category: "diagnosis" })
Always diagnose before suggesting fixes. Explain what you found. Store diagnoses for future reference — next time the same issue occurs, you'll recall it instantly.
Thresholds
Flag these to the user proactively:
- CPU sustained >90% for >5 minutes
- Memory usage >85%
- Swap usage >50%
- Any disk mount >90% full
- Load average > 2x number of cores
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.
- 12d ago First seen · 68 lines · 42 tokens per session scan A 27df20e95029
system-monitor is a skill published in the GitHub repository bolivian-peru/os-moda (117 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 474 once invoked, about $0.0002 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
makefile-generation
Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
analyzing-linux-kernel-rootkits
Detect kernel-level rootkits in Linux memory dumps using Volatility3 linux plugins (checksyscall, lsmod, hiddenmodules), rkhunter system scanning, and /proc vs /sys discrepancy analysis to identify hooked syscalls, hidden kernel modules, and tampered system structures.
devops-expert
Expert-level DevOps practices, culture, automation, and continuous delivery. Use when the user mentions CI/CD, automation, infrastructure, or culture, or when the task involves DevOps Culture or Culture & Process.
shell-scripting
Use this skill when writing bash or zsh scripts, parsing arguments, handling errors, or automating CLI workflows. Triggers on bash scripting, shell scripts, argument parsing, process substitution, here documents, signal trapping, exit codes, and any task requiring portable shell script development.
agent-self-improvement
Use when monitor performance of other skills, identify bottlenecks, suggest improvements, and auto-optimize the skill portfolio. Use when monitoring performance of other skills, identify bottlenecks, suggest improvements, and.