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/bouob/sysadmin-skills/problemnpx skills add bouob/sysadmin-skills --skill problemgit clone --depth 1 https://github.com/bouob/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.00233 | $0.01826 |
| Opus 5 | $0.00117 | $0.00913 |
| Sonnet 5 | $0.00047 | $0.00365 |
| Haiku 4.5 | $0.00023 | $0.00183 |
Grade A, and why
problem 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 yesterday.
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Management Workflow
Structured root cause investigation following ITIL v5 Problem Management. Produces a Problem record that tracks investigation progress from detection through permanent fix.
Related Skills (auto-loaded)
- itil — Problem Management process context, incident-to-problem handoff criteria
- done-ops — verification gate before closing the problem
Output
File: {OUTPUT_DIR}/problem-{YYYY-MM-DD}-{slug}.md
- slug: lowercase kebab-case summary, e.g.
vpn-weekly-disconnect,payment-gateway-timeout - Problem ID (
PRB-{YYYYMMDD}-{NNN}):{NNN}is a daily sequence number starting at 001. If the organization uses a ticketing system, use that system's ID instead.
Default output directory: ./problems/. If a docs/problems/ directory exists in the project, use that instead. Ask the user if neither exists.
All problem records are written in English. Preview content for the user in their preferred language before writing.
When to Create a Problem Record
Create a problem record when ANY of the following are true:
- The same incident has occurred 3 or more times
- An incident was closed with a workaround but no permanent fix
- Root cause is still unknown after the incident was resolved
- The incident revealed a systemic weakness that could affect other services
- A major incident (P1/P2) is resolved — proactive problem management recommended
Problem Types
| Type | Trigger | Example |
|---|---|---|
| Reactive | Created after one or more incidents have occurred | VPN drops after repeated user reports |
| Proactive | Created before an incident occurs (trending data, risk analysis) | Disk capacity trending toward full in 30 days |
Workflow
Step 1: Gather Information
Collect the following (use AskUserQuestion for missing items):
| Field | Required | Example |
|---|---|---|
| What is the recurring issue? | Yes | "Email service intermittently fails to send" |
| Linked incident IDs | Yes | "INC-20260401-001, INC-20260408-003" |
| How often does it occur? | Yes | "Every Monday morning, ~4 times this month" |
| Current workaround? | No | "Restarting the mail queue service fixes it temporarily" |
| Suspected cause? | No | "Memory leak after weekend batch job" |
What ships with it
2 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.
- yesterday First seen · 207 lines · 233 tokens per session scan A f42718a0787e
problem is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 233 tokens to every session and 1,826 once invoked, about $0.0012 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
servicenow-change-management
ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…
security-change-rollout-planning
Plan and execute a security change rollout across a service or fleet: classify the change into a time horizon (short / medium / long-term), triage affected systems by risk tier, select the appropriate rollout strategy with canarying and staged deployment, define communication strategy (internal and external), set…
abusing-dpapi-for-credential-access
Extract and decrypt Windows DPAPI-protected secrets (Credential Manager, browser logins/cookies, Wi-Fi credentials, KeePass keys) online or offline using SharpDPAPI, SharpChrome, Mimikatz, or Impacket's dpapi.py, including domain-wide decryption via the DPAPI backup key. Use during authorized red-team…
analyzing-apt-group-with-mitre-navigator
Query ATT&CK data with attackcti, mitreattack-python, and stix2, then build MITRE ATT&CK Navigator layers and multi-layer heatmap overlays mapping one or more APT groups' TTPs for detection-gap analysis. Use to compare threat-actor technique coverage, find gaps in detection engineering, or produce Navigator…
analyzing-bootkit-and-rootkit-samples
Analyzes bootkit and advanced rootkit malware infecting the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware for below-OS persistence, covering boot sector analysis, UEFI module inspection, and anti-rootkit detection. Use when compromise survives OS reinstallation or antivirus/EDR fails to detect…
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.