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 chipi/agentic-ai-homelab --skill ci-watchgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/ci-watch)<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/ci-watch"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/ci-watch/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/chipi/agentic-ai-homelab/ci-watch"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/ci-watch.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.00099 | $0.01618 |
| Opus 5.5 | $0.00040 | $0.00647 |
| Sonnet 5.5 | $0.00020 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
ci-watch 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ci-watch
After a push, the job is not done until CI on that commit is green. This watches it the same way every time, so the failures that happened when the loop was hand-written cannot recur:
| What went wrong (2026-10-16, podcast_scraper) | What the script does |
|---|---|
A short SHA on /commits/{sha}/check-runs returns 422; the hand loop swallowed it and saw "no checks" for 30 minutes |
Resolves the full SHA first, via git rev-parse or the commits API; an unknown ref exits 4 at once |
| The monitor expired at 30 minutes and nobody re-armed it | Stops before the deadline with RE-ARM ci-watch and exit 3 |
A fix's app-unit job was cancelled twice before it ran, and a cancelled check read as "done" |
Prints NOT RUN — cancelled; the next commit on <branch> is <sha>; the verdict is INCOMPLETE, never GREEN |
| The cause of a red job took several commands to find | Prints the failing job's log tail on the first failure, ##[error] lines first |
A green drill hid a failed tofu destroy (a fallback said "teardown OK") and a Node 20 deprecation, 2026-10-28; nobody read them |
Prints each check's warning and failure annotations under it; the GREEN verdict line counts warnings and names failures inside green checks as HIDDEN |
| On private repos a fine-grained token gets 403 on check-runs (it cannot hold Checks: read), so the watch saw nothing, 2026-10-31 | Falls back to the Actions jobs of the commit's workflow runs (a job id is its check-run id, so the log tail still works); the verdict says Actions jobs only |
The log tail never printed: gh 2.96 has no --allow-escape-sequences flag, so every fetch failed |
Plain gh api on the logs endpoint; ANSI codes are stripped afterwards |
Run it under the Monitor tool
Monitor(command: "python3 ~/.claude/skills/ci-watch/scripts/ci_watch.py <sha> --repo owner/name",
description: "CI on <sha>", timeout_ms: 1800000)
- Each stdout line is one event:
watching …, thenname: conclusionper check, a log tail block on the first failure, and oneVERDICT …line. --timeout-min(default 25) keeps it under the Monitor's 30-minute cap. On exit 3, start it again: a long suite (a 2-hour device tier, a 6-hour reprocess) needs several arms.- The SHA defaults to
HEAD;--repodefaults to the current directory's GitHub repo.
What ships with it
1 file 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.
- 3d ago Changed · +14 lines faa4594369d1
- 5d ago Changed · +3 lines f44b11085418
- 17d ago First seen · 76 lines · 99 tokens per session scan A 30bc913aa997
ci-watch is a skill published in the GitHub repository chipi/agentic-ai-homelab (3 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,618 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-18.
Other skills, from other repositories
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
nw-par-review-criteria
Quality dimensions and review checklist for devop reviews.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.
ship
Run the four pre-flight checks, then create the PR or validate a contributor branch without touching it. Use when you say ship it, ship this branch, or run pre-flight and open the PR, and run it after review. Do NOT use to open a PR without the gates (use push-pr), and do NOT use to run the review axes themselves (use…