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 JansenAnalytics/claudex --skill pr-monitorgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/pr-monitor)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/pr-monitor"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/pr-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/jansenanalytics/claudex/pr-monitor"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/pr-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.00059 | $0.00438 |
| Opus 5 | $0.00030 | $0.00219 |
| Sonnet 5 | $0.00012 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
pr-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 8d 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
PR / CI Monitor Skill
Use when: checking GitHub repo health, investigating why an alert fired, or adding a new repo to watch.
Check status of all repos now
node ${PR_MONITOR_HOME:-$HOME/projects/pr-monitor}/status.cjs
Run monitor now (dry run)
node ${PR_MONITOR_HOME:-$HOME/projects/pr-monitor}/monitor.cjs --dry-run
Run monitor and send real alerts if needed
node ${PR_MONITOR_HOME:-$HOME/projects/pr-monitor}/monitor.cjs
Cron
Runs every 30 minutes.
What it watches
- CI failures on main/master branch
- Open PRs awaiting review for >24h (non-draft, non-WIP)
- Open PRs with failing CI checks
- Stale PRs (no activity in 7 days)
Repos watched
All JansenAnalytics repos (auto-discovered). Exclusions in config.json.
Alert cooldown
4 hours per issue — won't spam on persistent failures.
Config
${PR_MONITOR_HOME:-$HOME/projects/pr-monitor}/config.json
Add a new repo (force-include)
node ${PR_MONITOR_HOME:-$HOME/projects/pr-monitor}/add-repo.cjs JansenAnalytics/some-new-repo
Files
- monitor.cjs — main cron script
- status.cjs — status table (reads last-run.json)
- add-repo.cjs — force-add a repo to config
- config.json — settings, exclusions, cooldowns
- state.json — cooldown tracking (auto-managed)
- last-run.json — last run results (read by status.cjs)
- monitor.log — log file
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.
- 8d ago First seen · 61 lines · 59 tokens per session scan A b9053baa14e0
pr-monitor is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 438 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.
code-review
Systematic code review SOP covering correctness, security, performance, and maintainability — plus GitHub PR review workflow (diff, inline comments, approve via gh/REST).
github-manager
GitHub operations - manage issues, pull requests, repositories, and workflows via GitHub API.
create-pr
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".