system-info

A read-only report of a computer’s operating system and available resources. It can show details such as processor load, memory, disk space, network interfaces, open ports, running programs, uptime, and boot time.

In plain words
What is it for?
Identify the operating system and hardware, check CPU, memory, swap, disk, and filesystem use, inspect processes and ports, and flag resource values that may indicate trouble.
Why use it?
It gives developers a focused view of the machine when investigating performance or system problems.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/bug-ops/zeph/system-info
Any agent
npx skills add bug-ops/zeph --skill system-info
Clone the repo
git clone --depth 1 https://github.com/bug-ops/zeph

Made for: Claude Code, Codex.

Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,848 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00100 $0.01848
Opus 5 $0.00050 $0.00924
Sonnet 5 $0.00020 $0.00370
Haiku 4.5 $0.00010 $0.00185

Measured 2d ago against content hash ece4076b3d7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

system-info scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. Test connectivity with `ping` or `curl`.
.zeph/skills/system-info/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

System Info

Collect host diagnostics and resource metrics.

Before running commands, detect the OS and load the matching reference for platform-specific syntax:

  • Linuxreferences/linux.md (procfs, sysfs, GNU coreutils)
  • macOSreferences/macos.md (sysctl, vm_stat, diskutil, system_profiler)
  • Windowsreferences/windows.md (PowerShell: Get-CimInstance, Get-Counter, Get-Process)

OS detection:

uname -s 2>/dev/null || echo Windows

Workflow

  1. Gather only the metrics the user requested — do not dump everything.
  2. Prefer read-only, non-invasive commands. Never change system settings unless explicitly asked.
  3. If a command is unavailable, check the OS reference for a fallback.
  4. Return a short summary with key numbers (percentages, GB, top processes).
  5. Flag values that indicate problems (see thresholds below).

Diagnostic categories

OS and kernel

Identify the operating system, distribution, kernel version, hostname, and architecture. Useful as a starting point for any troubleshooting session.

Key information to collect:

  • OS name and version (e.g., Ubuntu 24.04, macOS 15.2, Windows 11 23H2)
  • Kernel version
  • System architecture (x86_64, arm64)
  • Hostname

Uptime and load average

Determine how long the system has been running and its current load.

Interpreting load average (Unix):

  • Three numbers represent 1-minute, 5-minute, and 15-minute averages
  • Compare against CPU core count: load equal to core count means full utilization
  • Load consistently above core count indicates CPU contention
  • Rising trend (1min > 5min > 15min) means load is increasing

CPU

Inspect processor model, core count, current utilization, and per-core activity.

Metric Healthy Warning Critical
Overall utilization < 70% 70-90% > 90% sustained
Load avg / core count < 1.0 1.0-2.0 > 2.0
I/O wait < 10% 10-30% > 30%

Memory

Check total, used, free, available, cached, and buffered memory plus swap usage.

Read the full file on GitHub · 178 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 178 lines · 100 tokens per session scan A ece4076b3d7e

Subscribe to this mod's changes

system-info is a skill published in the GitHub repository bug-ops/zeph (57 stars, last pushed 8d ago), licensed MIT. It adds 100 tokens to every session and 1,848 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.