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/statuspagenpx skills add bouob/sysadmin-skills --skill statuspagegit 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/statuspage)<a href="https://agentmods.dev/skills/bouob/sysadmin-skills/statuspage"><img src="https://agentmods.dev/badge/skills/bouob/sysadmin-skills/statuspage.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.00094 | $0.01397 |
| Opus 5 | $0.00047 | $0.00698 |
| Sonnet 5 | $0.00019 | $0.00279 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
statuspage 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 4d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Page Update Workflow
Draft status page updates for incidents and scheduled maintenance. Produces updates compatible with Atlassian Statuspage and Instatus, following the standard four-phase incident lifecycle.
Related Skills (auto-loaded)
- comms — tone guidance, audience adaptation, statuspage templates
- done-ops — verification gate before posting "Resolved" updates
Output
File: {OUTPUT_DIR}/statuspage-{YYYY-MM-DD}-{slug}.md
- slug: lowercase kebab-case summary, e.g.
vpn-india-outage,firewall-maintenance
Default output directory: ./statuspage/. If a docs/statuspage/ directory exists in the project, use that instead. Ask the user if neither exists. A user-specified path takes precedence over all defaults.
All status page updates are written in English. Before writing to file, preview the content for the user in their preferred language.
Two Modes
Mode 1: Incident Update
For active or recent service incidents.
Mode 2: Maintenance Notice
For planned maintenance windows.
Determine the mode from the user's request. If unclear, ask.
Incident Update Workflow
Step 1: Gather Context
Collect from the user (use AskUserQuestion for missing items):
| Field | Required | Example |
|---|---|---|
| Which service? | Yes | "Email", "VPN", "Customer Portal" |
| What are users experiencing? | Yes | "Cannot send emails", "Slow page loads" |
| Current investigation status? | Yes | Investigating / Identified / Monitoring / Resolved |
| Priority level? | Yes (or derive) | P1 / P2 / P3 / P4 |
| Workaround available? | No | "Use webmail as alternative" |
| ETA for resolution? | No | "Estimated 2 hours" |
If an incident report exists (from the /incident skill), read it for context.
Step 2: Set Component Status
Map the situation to component statuses:
| Situation | Component Status | Incident Impact |
|---|---|---|
| Service completely unavailable | Major Outage | Critical |
| Service partially broken (subset of users) | Partial Outage | Major |
| Service slow or intermittent | Degraded Performance | Minor |
| Planned work in progress | Under Maintenance | Maintenance |
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.
- 4d ago First seen · 175 lines · 94 tokens per session scan A 479eb933175c
statuspage is a skill published in the GitHub repository bouob/sysadmin-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 1,397 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
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
deploy
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
detecting-compromised-cloud-credentials
Detecting compromised cloud credentials across AWS, Azure, and GCP by analyzing anomalous API activity, impossible travel patterns, unauthorized resource provisioning, and credential abuse indicators using GuardDuty, Defender for Identity, and SCC Event Threat Detection.
deploy-to-connect
Deploy or publish Python and R content to a Posit Connect server using rsconnect-python or the R rsconnect package. Handles interactive apps and dashboards, web APIs, rendered documents, and prepared bundles/manifests. Use whenever the user asks to deploy, publish, or redeploy content to Posit Connect, or mentions…
cloudflare-cron-triggers
Cloudflare Cron Triggers for scheduled Workers execution. Use for periodic tasks, scheduled jobs, or encountering handler not found, invalid cron expression, timezone errors.