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 lucasfcosta/backpressured --skill pr-monitoringgit clone --depth 1 https://github.com/lucasfcosta/backpressuredWrote 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/lucasfcosta/backpressured/pr-monitoring)<a href="https://agentmods.dev/skills/lucasfcosta/backpressured/pr-monitoring"><img src="https://agentmods.dev/badge/skills/lucasfcosta/backpressured/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/lucasfcosta/backpressured/pr-monitoring"><img src="https://agentmods.dev/badge/skills/lucasfcosta/backpressured/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.00076 | $0.01952 |
| Opus 5 | $0.00038 | $0.00976 |
| Sonnet 5 | $0.00015 | $0.00390 |
| Haiku 4.5 | $0.00008 | $0.00195 |
Grade A, and why
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Monitoring
Overview
Open is not landed. Green is not merged. A PR you opened is unfinished work until it has actually merged with nothing outstanding — or you have named a blocker only a human can clear. You are the machine that keeps watching so a human doesn't have to babysit the PR; declaring "done" at PR-open (or at a freshly-green CI) is exactly the human-backpressure you exist to replace.
Two traps the base instinct misses even when it resists "open = done":
- A green check can flip red. Late-starting jobs and slow stages mean an initial all-green is not a final all-green.
- The watch ends at merge, not at first green. New commits, reviewer comments, and conflicts arrive after CI goes green.
When to Use
- You (or the main agent) just opened a PR, or CI is running on one, and the goal is to get it merged.
- Asked "is it merged / did it land / is CI done yet?" on a PR you own.
- Tempted to report the task complete because the PR is open or CI just went green.
Not for: opening the PR itself; deciding whether to open one; code review of the diff (that is the reviewer skills). This is purely the watch-until-landed loop.
"Landed clean" — the sufficiency bar
Report done only when all hold; otherwise keep monitoring or name the blocker:
- PR state is MERGED (not just approved, not just green).
- Every required check is green — confirmed, not assumed (
statusCheckRollup). - No unresolved review-bot or human comments.
- No conflict (
mergeStateStatusis notDIRTY) and the branch is not stale (BEHIND) — ideallyCLEAN.
The monitoring loop
digraph pr_monitor {
"PR open" [shape=box];
"Watch checks to completion" [shape=box];
"All required checks green?" [shape=diamond];
"Read failing logs, fix root cause, push" [shape=box];
"Hold a green minute (≥60s continuously green)" [shape=box];
"Anything flipped red / new check started?" [shape=diamond];
"Comments or conflicts outstanding?" [shape=diamond];
"Address them (push fix / resolve / reply)" [shape=box];
"Merge if authorized" [shape=box];
"Merged?" [shape=diamond];
"STOP: name the human blocker" [shape=octagon];
"Landed clean — report done" [shape=doublecircle];
"PR open" -> "Watch checks to completion";
"Watch checks to completion" -> "All required checks green?";
"All required checks green?" -> "Read failing logs, fix root cause, push" [label="no"];
"Read failing logs, fix root cause, push" -> "Watch checks to completion";
"All required checks green?" -> "Hold a green minute (≥60s continuously green)" [label="yes"];
"Hold a green minute (≥60s continuously green)" -> "Anything flipped red / new check started?";
"Anything flipped red / new check started?" -> "Watch checks to completion" [label="yes — restart clock"];
"Anything flipped red / new check started?" -> "Comments or conflicts outstanding?" [label="no"];
"Comments or conflicts outstanding?" -> "Address them (push fix / resolve / reply)" [label="yes"];
"Address them (push fix / resolve / reply)" -> "Watch checks to completion";
"Comments or conflicts outstanding?" -> "Merge if authorized" [label="no"];
"Merge if authorized" -> "Merged?";
"Merged?" -> "STOP: name the human blocker" [label="no — needs approval/permission"];
"Merged?" -> "Landed clean — report done" [label="yes"];
}
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 · 117 lines · 76 tokens per session scan A 2b313cda712a
pr-monitoring is a skill published in the GitHub repository lucasfcosta/backpressured (63 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 1,952 once invoked, about $0.0004 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
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.