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 cyanheads/devops-status-mcp-server --skill devops-status-guidegit clone --depth 1 https://github.com/cyanheads/devops-status-mcp-serverWrote 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/cyanheads/devops-status-mcp-server/devops-status-guide)<a href="https://agentmods.dev/skills/cyanheads/devops-status-mcp-server/devops-status-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/devops-status-mcp-server/devops-status-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cyanheads/devops-status-mcp-server/devops-status-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/devops-status-mcp-server/devops-status-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00109 | $0.03063 |
| Opus 5.5 | $0.00044 | $0.01225 |
| Sonnet 5.5 | $0.00022 | $0.00613 |
| Haiku 4.5 | $0.00011 | $0.00306 |
Grade A, and why
devops-status-guide 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 5d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
- Vendor health, incidents, and maintenance windows as each vendor publishes them on its own status page, plus TLS and DNS probes of any public domain. Keyless.
- No tool measures a vendor's service. A status page is the vendor's own account and often trails real impact, so a clean reading means the vendor has posted nothing, not that the user's path works. A clean
devops_check_certsordevops_check_dnson a vendor endpoint shows that DNS and TLS work from the server's network, not that the API answers. - Probes run from wherever the server runs.
devops_check_certsrefuses a host that resolves to a private, loopback, or metadata address, anddevops_check_dnsrefuses such an address as a resolver, unless the server was started withDEVOPS_STATUS_ALLOW_PRIVATE_TARGETS=true, so an internal host or resolver needs a local server started that way.devops_check_dnsqueries any name at public resolvers, including one whose records point at private addresses. A deployment that disables active probes has no probe tools, anddevops_suggest_actionnamesdigandopensslinstead.
Identifiers
| Input | Where it comes from |
|---|---|
| Vendor slug | devops_list_vendors, whose query matches slugs and display names. The status tools take a slug in any letter case but not a display name ("gcp" works, "Google Cloud" fails); of the tools that take a vendor, only devops_suggest_action accepts a display name. |
| Unlisted vendor | Its Atlassian Statuspage base URL, scheme included (https://status.example.com); a bare host is rejected. A row whose error is an HTTP 404 or unparseable JSON means the URL is not a Statuspage base URL, and no other backend is reachable by URL. |
| Backend | api_type in the devops-status://vendors/{slug} resource. Native adapters serve aws, gcp, azure, azure-devops, gitlab and neon (Status.io), slack, redis-cloud (Firehydrant), and the nine Datadog site slugs, datadog (US1) and datadog-us3 through datadog-us2-fed (Datadog); every other slug is Statuspage. |
| Atlassian product | Jira, Confluence, Bitbucket, Trello, Opsgenie, and several other Atlassian products each have an entry; devops_list_vendors with query "atlassian" lists them. A product without one, such as Loom, takes its own Statuspage base URL (https://loom.status.atlassian.com). atlassian itself reads the umbrella page, which has no components and posts only cross-product incidents, so it never stands in for a product. |
| One incident | No tool fetches an incident by id. Find it again with devops_get_incidents, using match on title words and since/until around its start. |
| Next page | nextOffset for incidents. For a component list that continues past the page, pass the vendor's next_component_offset, from a devops_status_check or devops_watch_stack row, as component_offset to devops_status_check in detailed mode, with the same component_filter. |
| DNS resolver | IP literals only. To ask a zone's own nameservers, query NS, then A for each nameserver host, then pass those addresses as resolvers. |
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.
- 5d ago Changed · +2 lines 03f104c01b8a
- 6d ago First seen · 76 lines · 109 tokens per session scan A 01dafc8c54e9
devops-status-guide is a skill published in the GitHub repository cyanheads/devops-status-mcp-server (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 109 tokens to every session and 3,063 once invoked, about $0.0004 per session on Opus 5.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-10-31.
devops-status-guide compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| devops-status-guidecyanheads/devops-status-mcp-server | Skill | 3 | 6d ago | Apache-2.0 | A | 109 | Claude Code |
| api-workerscyanheads/oecd-mcp-server | Skill | 4 | 3d ago | Apache-2.0 | A | 51 | Claude Code |
| api-workerscyanheads/internet-archive-mcp-server | Skill | 4 | 9d ago | Apache-2.0 | A | 51 | Claude Code |
| api-workerscyanheads/usgs-water-mcp-server | Skill | 3 | 8d ago | Apache-2.0 | A | 51 | Claude Code |
| api-workerscyanheads/national-parks-mcp-server | Skill | 3 | 9d ago | Apache-2.0 | A | 51 | Claude Code |
| api-workerscyanheads/smithsonian-mcp-server | Skill | 2 | 5d ago | Apache-2.0 | A | 51 | Claude Code |
| api-workerscyanheads/osv-advisory-mcp-server | Skill | 2 | 5d ago | Apache-2.0 | A | 51 | Claude Code |