monitor

monitor is a skill for Claude Code, Codex from gspencergoog/skills. It costs 166 tokens per session (2,256 once invoked), scanned A, original, Apache-2.0.

A watcher for GitHub pull requests, which are proposed code changes submitted for review. It tracks review status, automated checks, merge conflicts, assignments, and changes across related requests.

In plain words
What is it for?
It is for monitoring one or more pull requests, showing their current state, retrying certain flaky checks, and waking the agent for fixes or completion.
Why use it?
It removes the need to repeatedly check pull requests and alerts the coding agent when a failed check or conflict needs attention.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It is for monitoring one or more pull requests, showing their current state, retrying certain flaky checks, and waking the agent for fixes or completion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gspencergoog/skills/monitor
Install

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.

Any agent
npx skills add gspencergoog/skills --skill monitor
Clone the repo
git clone --depth 1 https://github.com/gspencergoog/skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for monitor

README.md
[![agentmods](https://agentmods.dev/badge/skills/gspencergoog/skills/monitor/github.svg)](https://agentmods.dev/skills/gspencergoog/skills/monitor)
Your own site
<a href="https://agentmods.dev/skills/gspencergoog/skills/monitor"><img src="https://agentmods.dev/badge/skills/gspencergoog/skills/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.

agentmods 80×15 button for monitor

Your own site · 80×15
<a href="https://agentmods.dev/skills/gspencergoog/skills/monitor"><img src="https://agentmods.dev/badge/skills/gspencergoog/skills/monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00166 $0.02256
Opus 5.5 $0.00066 $0.00902
Sonnet 5.5 $0.00033 $0.00451
Haiku 4.5 $0.00017 $0.00226

Measured today against content hash 018d69736d2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 today.

The scan reads SKILL.md. This mod also ships 17 executable files (scripts/a2ui_board.py, scripts/diff_events.py, scripts/gh_client.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/monitor/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Monitor (/monitor)

monitor watches one or more GitHub pull requests across a session. Its helper script, scripts/monitor_prs.py, polls GitHub notifications (If-Modified-Since, free 304 responses every 60 seconds) alongside periodic GraphQL refreshes (every 120 seconds) and diffs each pull request against a per-conversation state file.

On every refresh, monitor_prs.py writes <scratch>/monitor/board.a2ui and appends stack_board updates directly to the a2ui-pane conversation JSONL store (~/.gemini/jetski/plugin_data/a2ui-pane/conversations/<conversationId>.jsonl), streaming live badge and CI ETA updates to the open pane at zero LLM tokens. A lightweight flash watcher subagent runs the blocking loop with --actionable-only, handles one-time flaky CI reruns and failing-log capture, and wakes the main agent only when workspace remediation or terminal completion occurs.

Read references/action_policy.md before acting on any event and references/output_schema.md for the JSON payload contract, CLI flags, event kinds, and exit codes.

1. Resolve Target Pull Requests

Pass the target pull requests explicitly on the monitor_prs.py command line. Never rely on the script to guess targets from the current git branch:

  1. Include every pull request the user names in their prompt (owner/repo#123, a pull request URL, or #123 with --repo owner/repo).
  2. Add every open pull request already discussed or created in the current conversation.
  3. Pass --stack when the user asks to watch a stack or when any target pull request is part of a branch stack.

Store all monitor files inside the conversation scratch directory:

  • State snapshot: <conversation-scratch-dir>/monitor/state.json
  • Event history log: <conversation-scratch-dir>/monitor/events.jsonl
  • Latest output file: <conversation-scratch-dir>/monitor/last.json
  • A2UI Express DSL file: <conversation-scratch-dir>/monitor/board.a2ui
  • Captured CI failure logs: <conversation-scratch-dir>/monitor/ci_<repo>_<pr>.log

Read the full file on GitHub · 104 lines

Changes

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.

  1. today Changed · +1 lines 018d69736d2a
  2. 2d ago First seen · 103 lines · 166 tokens per session scan A 30503a5cb4b2

Subscribe to this mod's changes

monitor is a skill published in the GitHub repository gspencergoog/skills (2 stars, last pushed today), licensed Apache-2.0. It adds 166 tokens to every session and 2,256 once invoked, about $0.0007 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-28.