Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agigante80/actual-mcp-server/main/.claude/commands/ci-health.mdgit clone --depth 1 https://github.com/agigante80/actual-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/commands/agigante80/actual-mcp-server/ci-health)<a href="https://agentmods.dev/commands/agigante80/actual-mcp-server/ci-health"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/ci-health/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/commands/agigante80/actual-mcp-server/ci-health"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/ci-health.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.00000 | $0.01275 |
| Opus 5 | $0.00000 | $0.00638 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
ci-health 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Health Monitor
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
Process
Execute these phases in order. Stop early if all workflows are passing.
Phase 1: Discover and assess workflows
Auto-discover all workflow files:
ls .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null
Detect the working branch (always develop for this project, never push fixes directly to main):
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "develop"
For each discovered workflow, check the latest run on develop:
gh run list --workflow <workflow-file> --branch develop --limit 1 --json databaseId,conclusion,createdAt,name -q '.[0]'
For each failing run, get failed jobs and error logs:
gh run view <RUN_ID> --json jobs --jq '.jobs[] | select(.conclusion == "failure") | .name'
gh run view <RUN_ID> --log-failed 2>&1 | tail -150
Report a summary table:
| Workflow | Status | Failed jobs |
|---|---|---|
| ci-cd.yml | pass/fail | job1, job2 |
| dependency-update.yml | pass/fail | - |
If ALL workflows are passing, report "All workflows green" and stop.
Classify governance workflows separately. A red release / version-gate failure (for
example, scripts/version-bump.js aborting because the local VERSION is behind the latest
published tag, or a version-bump enforcement step failing) is an intentional governance
signal, not a CI breakage. Do not file a P0 bug for it and do not carry it into the fix
phases; surface it as "action: run git fetch origin && git merge origin/main, then bump per
the release process" and move on (see Phase 4). Releases are a human responsibility in this
project (release:* scripts are never run by automation).
Phase 2: Create tickets for failures
For each failing job:
- Check for an existing open ticket to avoid duplicates:
gh issue list --search "fix(ci): <job-name-keyword>" --state open --limit 1
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.
- 11d ago First seen · 142 lines · 0 tokens per session scan A 1eed664ef88c
ci-health is a command published in the GitHub repository agigante80/actual-mcp-server (54 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,275 tokens. 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-30.
Other commands, from other repositories
pr-quality-gate-devops
You are reviewing a pull request for CI/CD, build, deployment, and infrastructure concerns.
pr-quality-gate-architect
You are reviewing a pull request for architectural design and system structure concerns.
pr-quality-gate-code-quality
You are reviewing a pull request for the maintainability of the code it changes: how cohesive, loosely coupled, encapsulated, testable, and non-redundant the touched code is, and whether the author left each file at least as clean as they found it.
pr-quality-gate-decision-rigor
You are reviewing a pull request for the quality of the reasoning behind a decision, not just the code that implements it.
pr-quality-gate-qa
You are a rigorous QA reviewer. Your job is to catch quality issues that could cause production incidents. Be skeptical and thorough.
pr-quality-gate-agent-safety
You are reviewing a pull request for agent-safety risk: changes that alter how an autonomous agent behaves, what it can run, or what guardrails it must clear before acting.