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 gspencergoog/skills --skill monitorgit clone --depth 1 https://github.com/gspencergoog/skillsWrote 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/gspencergoog/skills/monitor)<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.
<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>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.00166 | $0.02256 |
| Opus 5.5 | $0.00066 | $0.00902 |
| Sonnet 5.5 | $0.00033 | $0.00451 |
| Haiku 4.5 | $0.00017 | $0.00226 |
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.
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 — 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:
- Include every pull request the user names in their prompt (
owner/repo#123, a pull request URL, or#123with--repo owner/repo). - Add every open pull request already discussed or created in the current conversation.
- Pass
--stackwhen 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
What ships with it
24 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.
- references/action_policy.md 7.1 KB
- references/output_schema.md 10 KB
- scripts/a2ui_board.py 20 KB runs code
- scripts/diff_events.py 17 KB runs code
- scripts/fixtures/notifications_200.txt 684 B
- scripts/fixtures/notifications_304.txt 83 B
- scripts/fixtures/pr_ci_failed.json 5.2 KB
- scripts/fixtures/pr_open_ci_running.json 4.8 KB
- scripts/fixtures/pr_stack.json 2.5 KB
- scripts/gh_client.py 8.3 KB runs code
- scripts/models.py 11 KB runs code
- scripts/monitor_prs.py 25 KB runs code
- scripts/normalize.py 9.2 KB runs code
- scripts/notifications.py 4.1 KB runs code
- scripts/state.py 5.3 KB runs code
- scripts/test_a2ui_board.py 12 KB runs code
- scripts/test_diff_events.py 8.5 KB runs code
- scripts/test_gh_client.py 4.3 KB runs code
- scripts/test_models.py 4.9 KB runs code
- scripts/test_monitor_prs.py 15 KB runs code
- scripts/test_normalize.py 2.9 KB runs code
- scripts/test_notifications.py 2.6 KB runs code
- scripts/test_state.py 4.3 KB runs code
- scripts/testing.py 4.2 KB runs code
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.
- today Changed · +1 lines 018d69736d2a
- 2d ago First seen · 103 lines · 166 tokens per session scan A 30503a5cb4b2
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.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.