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 ckorhonen/swe-skills --skill merged-pr-monitoringgit clone --depth 1 https://github.com/ckorhonen/swe-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/ckorhonen/swe-skills/merged-pr-monitoring)<a href="https://agentmods.dev/skills/ckorhonen/swe-skills/merged-pr-monitoring"><img src="https://agentmods.dev/badge/skills/ckorhonen/swe-skills/merged-pr-monitoring/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/ckorhonen/swe-skills/merged-pr-monitoring"><img src="https://agentmods.dev/badge/skills/ckorhonen/swe-skills/merged-pr-monitoring.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.00106 | $0.01603 |
| Opus 5 | $0.00053 | $0.00801 |
| Sonnet 5 | $0.00021 | $0.00321 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade A, and why
swe:merged-pr-monitoring 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 12d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SWE Merged PR Monitoring
What This Skill Does
Use this skill to connect merged code changes to production evidence without guessing.
The expected output is a short, PR-by-PR report that answers:
- What merged
- Whether it deployed
- What likely changed in production
- What the observable impact was, if any
When To Use
Use this skill when the user wants to:
- Review the production impact of recent merged PRs
- Check whether a change reached production and moved metrics
- Compare pre- and post-deploy behavior for a scoped set of merges
- Produce a concise engineering readout tied to merged GitHub work
Do Not Use
Do not use this skill for:
- Pre-merge code review
- Root-cause analysis with no scoped PR set
- Generic service monitoring not tied to merged changes
- Product analytics reporting unrelated to deploys
Inputs To Confirm
Confirm or infer:
- Repository or service scope
- Author filter, if any
- Time window
- Production environment or environments to check
- Available deployment and observability sources
If the request leaves scope ambiguous, ask for the repo set, author filter, and time window before proceeding.
Tooling Stance
This skill is tool agnostic.
Use whichever deployment and observability sources are available, such as:
- Datadog
- Grafana
- CloudWatch
- Prometheus
- Internal deploy dashboards
- Release logs
- CI or CD systems
- Service-specific metrics or tracing tools
Prefer the source that gives the strongest direct evidence. If multiple sources are available, cross-check them when practical.
Instructions
Step 1: Define Scope Precisely
Respect the exact repositories, author filters, and timeframe requested by the user.
If the user defines a conditional timeframe such as last 24 hours, or since last Friday if today is Monday, apply it exactly.
Step 2: Collect The Merged PR Set
For each PR in scope, capture:
- PR number
- Title
- Link
- Merge time
Do not skip the merge timestamp. It anchors the later deployment comparison.
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.
- 12d ago First seen · 264 lines · 106 tokens per session scan A 9b985adad757
swe:merged-pr-monitoring is a skill published in the GitHub repository ckorhonen/swe-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 1,603 once invoked, about $0.0005 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
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.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.