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/commsnpx skills add bouob/sysadmin-skills --skill commsgit 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.00054 | $0.00718 |
| Opus 5 | $0.00027 | $0.00359 |
| Sonnet 5 | $0.00011 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
comms 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 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.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IT Operations Communication
Templates and guidance for stakeholder communication during incidents, changes, and maintenance. All output in English by default; preview in the user's language before writing to file.
Related Skills
- /incident — loads this skill for incident notifications
- /statuspage — loads this skill for status page updates
- itil — provides priority classification that determines communication tone
Core Principles
- Impact-focused, not technical — describe what users experience, not what broke internally
- Honest but controlled — acknowledge the issue without exposing sensitive infrastructure details
- Predictable cadence — always include "Next update by [time]" to reduce anxiety
- Severity-appropriate tone — match urgency to priority level
- Audience-aware — tailor detail level to the recipient group
Tone by Priority Level
| Priority | Tone | Cadence | Example Opening |
|---|---|---|---|
| P1 | Urgent, direct, action-oriented | Every 15-30 min | "We are experiencing a major service disruption..." |
| P2 | Serious, informative | Every 30-60 min | "We are aware of issues affecting..." |
| P3 | Informative, measured | When meaningful updates occur | "Some users may notice..." |
| P4 | Routine, brief | At resolution | "A minor issue has been identified..." |
Audience Adaptation
| Audience | Detail Level | Focus |
|---|---|---|
| End users | Minimal technical detail | What is affected, workaround, ETA |
| Management | Business impact + timeline | Revenue/productivity impact, resource allocation, ETA |
| Technical teams | Full technical detail | Systems affected, error codes, diagnostic steps |
| External (statuspage) | Impact-focused, no internal names | Service status, user-facing impact, ETA |
What to Include vs Exclude
| Include | Exclude |
|---|---|
| Affected service (user-facing name) | Internal system names, IP addresses |
| User impact description | Root cause details during active incidents |
| Current status and actions being taken | Names of individuals responsible |
| Estimated time to resolution (if known) | Security-sensitive information |
| Workaround instructions (if available) | Blame or fault attribution |
| Next update time | Speculative root cause |
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.
- 2d ago First seen · 74 lines · 54 tokens per session scan A 2becce430186
comms is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 718 once invoked, about $0.0003 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.