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 agentmods add skills/joris887/exosuit/pr-statusnpx skills add joris887/exosuit --skill pr-statusgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/pr-status)<a href="https://agentmods.dev/skills/joris887/exosuit/pr-status"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/pr-status.svg" alt="Measured on agentmods" 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.00031 | $0.00442 |
| Opus 5 | $0.00015 | $0.00221 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
pr-status 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 6d 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-status
Check status of your pull requests:
Current Open PRs (auto-fetched)
!gh pr list --author @me --state open --json number,title,state,reviewDecision,statusCheckRollup --template '{{range .}}PR #{{.number}}: {{.title}} Review: {{.reviewDecision}} | Checks: {{range .statusCheckRollup}}{{.state}} {{end}} {{end}}' 2>/dev/null || echo "No open PRs or gh not configured"
1. Analyze PR Status
2. For Each Open PR
gh pr view <number> --json state,reviewDecision,statusCheckRollup,mergeable
gh pr checks <number>
3. Status Summary
## PR Status Report
### PR #[number]: [title]
- **Branch**: [branch-name]
- **Review Status**: [Approved/Changes Requested/Pending]
- **Checks**: [Passing/Failing/Pending]
- **Mergeable**: [Yes/No - reason if no]
### Recommended Actions
- [Action based on status]
4. Available Actions
Based on PR status, offer options:
If Approved + Checks Passing:
gh pr merge --squash --delete-branch
If Changes Requested:
- View review comments:
gh pr view <number> --comments - Address feedback and push updates
If Checks Failing:
- View failed checks:
gh pr checks <number> - Fix issues and push
If Pending Review:
- Wait or request review:
gh pr edit <number> --add-reviewer <user>
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.
- 6d ago First seen · 69 lines · 31 tokens per session scan A 9641db3793cd
pr-status is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 16d ago), licensed MIT. It adds 31 tokens to every session and 442 once invoked, about $0.0002 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-update-infos-release
Update Codex releases tracking (guide + landing + version bump).
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…