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/ericboehs/claude-plugins/watch-cinpx skills add ericboehs/claude-plugins --skill watch-cigit clone --depth 1 https://github.com/ericboehs/claude-pluginsWhat 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.00043 | $0.00364 |
| Opus 5 | $0.00022 | $0.00182 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
watch-ci 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 2d 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.
What it actually says
watch-ci
Monitor GitHub Actions CI status for the current branch, waiting until all checks pass or fail.
Steps
1. Run the watch script
Run ${CLAUDE_PLUGIN_ROOT}/scripts/watch-ci.sh and wait for it to exit. It auto-detects the current branch, checks for a PR first (using gh pr checks --json), and falls back to workflow runs if no PR exists. It polls every 10 seconds by default. To use a custom interval, pass it as the first argument (e.g., watch-ci.sh 30). Minimum is 5 seconds.
If CLAUDE_PLUGIN_ROOT is not set, find the script relative to this SKILL.md (../../scripts/watch-ci.sh).
2. Report the result
When the script exits:
- Exit code 0 means all checks passed. Report success.
- Non-zero exit means checks failed. The script will have printed failure logs. Summarize the failures for the user.
If the user wants to investigate failures, offer to:
- Read the failure logs in detail
- Open the GitHub Actions run URL
- Help fix the failing code
Important notes
- This skill just monitors — it does not push, commit, or modify code.
- If no CI runs are found, suggest the user push their branch first.
- The script exits automatically when checks complete. Do not kill it early unless the user asks.
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.
- 2d ago First seen · 36 lines · 43 tokens per session scan A 30673615014a
watch-ci is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 364 once invoked, about $0.0002 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
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.