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 bendrucker/claude --skill actions-monitorgit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/actions-monitor)<a href="https://agentmods.dev/skills/bendrucker/claude/actions-monitor"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/actions-monitor/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/bendrucker/claude/actions-monitor"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/actions-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01056 |
| Opus 5 | $0.00015 | $0.00528 |
| Sonnet 5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
github:actions-monitor 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Actions Monitor
Watch a PR, branch, or specific run's GitHub Actions progress and react to failures by pulling logs through the github:logs agent. The watch script handles state tracking and deduplication. This skill starts it, reacts to events, and stops it.
Target
$ARGUMENTS
- A GitHub PR URL runs in PR mode. Owner and repo come from the URL, so PR mode works from any working directory.
- A branch name runs in branch mode.
- A run ID runs in run-id mode, watching a specific workflow run directly (covers
workflow_dispatch, manual triggers, and re-runs). - No argument: derive the current PR with
gh pr view --json url --jq '.url'. If the branch has no PR, fall back to branch mode with the current branch name.
Branch and run-id mode infer the repo from git remote get-url origin; pass --repo <owner/repo> to override.
Workflow
Start the monitor
Invoke Monitor with persistent: true on the watch script, with exactly one mode flag:
bun ${CLAUDE_SKILL_DIR}/scripts/watch.ts --pr <pr-url>
bun ${CLAUDE_SKILL_DIR}/scripts/watch.ts --branch <name> [--repo <owner/repo>]
bun ${CLAUDE_SKILL_DIR}/scripts/watch.ts --run-id <id> [--repo <owner/repo>]
Optional flags: --interval <seconds>, --max-minutes <N>, --queued-timeout <minutes>, --api-error-threshold <N>. Omit --interval to let the script derive one from recent run durations in PR/branch mode; run-id mode uses a 180s default.
Event schema
The script emits one JSON object per line on stdout:
{"type":"status","state":"running|failing|success","sha":"...","run_id":"..."}{"type":"conflicts","sha":"..."}(PR mode only){"type":"mergeable-unknown","sha":"..."}(PR mode only){"type":"queued-timeout","minutes":N}{"type":"api-error","consecutive":N}{"type":"rate-limited","retry_after":"..."}{"type":"pr-closed"}(PR mode only; also fires if the branch is deleted){"type":"merged"}(PR mode only){"type":"max-time-reached","minutes":60}
What ships with it
3 files 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.
- 6d ago Changed · -1 lines 8d6bf6e2c97a
- 13d ago First seen · 78 lines · 29 tokens per session scan A e5d06b889c46
github:actions-monitor is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,056 once invoked, about $0.0001 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-30.
Other skills, from other repositories
setup-solution
Creates a Dataverse publisher and solution, then adds Power Pages site components to the solution for ALM and deployment management. Use when asked to: "create solution", "set up solution", "add to solution", "package site into solution", "create publisher", "solutionize my site", or "set up ALM for my site".
setup-pipeline
Sets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the Power Platform — no external infrastructure required. Use when asked to: "set up ci/cd", "create pipeline", "setup pipeline", "set up power platform pipelines", "create…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
force-link-environment
Force-links a development or target environment to a Power Platform Pipelines host, overriding any existing association with a previous host. Use when creating a deploymentenvironments record fails with "this environment is already associated with another pipelines host", or when intentionally migrating an environment…
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.