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/itilnpx skills add bouob/sysadmin-skills --skill itilgit clone --depth 1 https://github.com/bouob/sysadmin-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/bouob/sysadmin-skills/itil)<a href="https://agentmods.dev/skills/bouob/sysadmin-skills/itil"><img src="https://agentmods.dev/badge/skills/bouob/sysadmin-skills/itil.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00090 | $0.01603 |
| Opus 5 | $0.00045 | $0.00801 |
| Sonnet 5 | $0.00018 | $0.00321 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
itil 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ITIL (Version 5) Framework Reference
ITIL 4 guidance for IT operations workflows. Provides process definitions, classification standards, and best practices for Incident Management and Change Enablement.
Related Skills
- /incident — loads this skill for severity classification and incident process
- /change-request — loads this skill for change types and CAB review process
- done-ops — verification gate for operations tasks
Dual Classification: SEV (Scope) + P (Order)
Incidents are classified on two independent axes:
| Axis | Measures | Determined by | Question |
|---|---|---|---|
| SEV (Severity) | Objective technical impact scope | Impact breadth × depth | "How widespread and severe is the damage?" |
| P (Priority) | Subjective business handling order | Impact × Urgency | "What gets fixed first?" |
Workflow: Assign SEV first (objective), then determine P (adds business urgency context).
Step 1 — Severity Classification (SEV1-SEV4)
SEV measures the objective scope and depth of impact:
| Level | Scope | Definition | Example |
|---|---|---|---|
| SEV-1 Critical | All users / all regions | Core service completely down, no workaround | Production DB offline, auth service failure |
| SEV-2 Major | Many users or major function | Significant degradation, partial workaround | Payment fails for 30% of users, single-region outage |
| SEV-3 Minor | Subset of users, non-critical | Limited impact, workaround available | Search suggestions broken, one printer queue stuck |
| SEV-4 Low | Single user or negligible | Cosmetic, proactive, informational | UI alignment bug, capacity threshold approaching |
Step 2 — Priority Classification (P1-P4)
P determines the handling order by combining Impact with business Urgency:
| High Urgency | Medium Urgency | Low Urgency | |
|---|---|---|---|
| High Impact | P1 — Critical | P2 — High | P3 — Medium |
| Medium Impact | P2 — High | P3 — Medium | P4 — Low |
| Low Impact | P3 — Medium | P4 — Low | P4 — Low |
What ships with it
7 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.
- 3d ago First seen · 128 lines · 90 tokens per session scan A 2ecf7926fd96
itil is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 1,603 once invoked, about $0.0005 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…
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-certificate-transparency-for-phishing
Monitor Certificate Transparency logs using crt.sh and Certstream to detect phishing domains, lookalike certificates, and unauthorized certificate issuance targeting your organization.
analyzing-dns-logs-for-exfiltration
Analyzes DNS query logs to detect data exfiltration via DNS tunneling, DGA domain communication, and covert C2 channels using entropy analysis, query volume anomalies, and subdomain length detection in SIEM platforms. Use when SOC teams need to identify DNS-based threats that bypass traditional network security…
analyzing-macro-malware-in-office-documents
Analyzes malicious VBA macros embedded in Microsoft Office documents (Word, Excel, PowerPoint) to identify download cradles, payload execution, persistence mechanisms, and anti-analysis techniques. Uses olevba, oledump, and VBA deobfuscation to extract the attack chain. Activates for requests involving Office macro…