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 AI-Shell-Team/aish --skill diagnose_system_laggit clone --depth 1 https://github.com/AI-Shell-Team/aishWrote 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/ai-shell-team/aish/diagnose_system_lag)<a href="https://agentmods.dev/skills/ai-shell-team/aish/diagnose_system_lag"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/diagnose_system_lag.svg" alt="Measured on agentmods" 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.00078 | $0.01985 |
| Opus 5 | $0.00039 | $0.00992 |
| Sonnet 5 | $0.00016 | $0.00397 |
| Haiku 4.5 | $0.00008 | $0.00198 |
Grade A, and why
diagnose_system_lag 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 8d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System lag diagnosis
Short-path, read-only diagnosis for lag, slowness, resource pressure, or a recent unexpected reboot on this host.
Out of scope: full sos collection, long-running health baselines, cloud VPC troubleshooting, auto config changes or killing processes. Use sosreport-analyzer, deepin-sysassist, or other skills for those.
Rules
- Read-only: do not change config, kill processes, drop caches, tune sysctl, or unload modules.
- Symptom-first: decide what to probe from the user's report; do not run a fixed full command list every time.
- Stop when enough: stop once the symptom is explained and key objects (process / mount / device) are named.
- Follow-ups fill gaps only: the next probe answers “what is still missing”, not “scan every focus again”.
- Advice needs confirmation: prefer action targets; give concrete kill/restart commands only if asked, and remind the user to save work.
- Isolated sessions: do not run report-writing scripts under this skill (for example
scripts/diagnose.sh). - Honest probes: if a tool is missing or a probe fails, state that in Evidence—do not treat it as “no problem found”.
Workflow
Understand symptom → quick check (only if vague) → focused probes → answer
↑ stop when evidence is enough ↑
1. Understand the symptom
| User report | Focus | First step |
|---|---|---|
| Slow / high load / no specifics | Unknown | Quick check |
| Low memory, Swap, OOM, process killed | Memory | Memory probes |
| Copy/open large files stalls, disk noise, frozen I/O | Disk | Disk probes |
| High CPU, fans spinning, one process pegged | CPU | CPU probes |
| Slow/unreachable network (local host side) | Network | Local network probes |
| Sudden reboot, black screen then recovery, unclean shutdown | Incident | Reboot/crash probes |
Named apps (browser, WPS, Java, a service) are suspects under the matching focus—not a separate workflow.
What ships with it
6 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.
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.
- 8d ago First seen · 219 lines · 78 tokens per session scan A 1539bdac6486
diagnose_system_lag is a skill published in the GitHub repository AI-Shell-Team/aish (530 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 1,985 once invoked, about $0.0004 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
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
flare
Manage Flare error tracking and performance monitoring using the flare CLI. Use when the user wants to list, triage, resolve, snooze, or debug errors; manage projects; create projects and retrieve API keys; check error counts; investigate slow routes, queries, jobs, or commands; view aggregated performance data and…
audit-architecture
Run an application-wide, read-only architecture audit that finds materially useful simplifications in a codebase's data structures, state representation, control flow, algorithms, and ownership boundaries. Fans out bounded read-only agents per subsystem, verifies every finding against the repo, and ranks results P0 to…
completion-script-generator
Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…