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 curiositech/windags-skills --skill ci-status-checkergit clone --depth 1 https://github.com/curiositech/windags-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/curiositech/windags-skills/ci-status-checker)<a href="https://agentmods.dev/skills/curiositech/windags-skills/ci-status-checker"><img src="https://agentmods.dev/badge/skills/curiositech/windags-skills/ci-status-checker/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/curiositech/windags-skills/ci-status-checker"><img src="https://agentmods.dev/badge/skills/curiositech/windags-skills/ci-status-checker.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.00119 | $0.03581 |
| Opus 5 | $0.00060 | $0.01791 |
| Sonnet 5 | $0.00024 | $0.00716 |
| Haiku 4.5 | $0.00012 | $0.00358 |
Grade A, and why
ci-status-checker 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 357 lines · 119 tokens per session scan A d16ae57877a3
ci-status-checker is a skill published in the GitHub repository curiositech/windags-skills (10 stars, last pushed 1mo ago), with no licence file. It adds 119 tokens to every session and 3,581 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
github-actions-docs
GitHub Actions — workflows, events, jobs, runners, contexts, expressions, secrets, caching, reusable workflows.
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
GitHub CI Fix Debugging
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
GitHub Actions CI Patterns
Use this skill when adding or debugging GitHub Actions workflows and you want repeatable CI behavior, minimal permissions, and clear failure logs.
github-actions-ci
Structure GitHub Actions workflows — jobs, steps, caching, matrix builds, secrets, and a quality gate that blocks merges.
auto-dev-setup
A set of instructions for setting up an automated development workflow with human review. It uses GitHub Actions, which run tasks automatically when events occur in a GitHub repository.