Borrowing it
Nothing to install: this file belongs to jerseycheese/Narraitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jerseycheese/Narraitor/main/.claude/agents/pr-merge-issue-updater.mdgit clone --depth 1 https://github.com/jerseycheese/NarraitorWrote 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/agents/jerseycheese/narraitor/pr-merge-issue-updater)<a href="https://agentmods.dev/agents/jerseycheese/narraitor/pr-merge-issue-updater"><img src="https://agentmods.dev/badge/agents/jerseycheese/narraitor/pr-merge-issue-updater/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/agents/jerseycheese/narraitor/pr-merge-issue-updater"><img src="https://agentmods.dev/badge/agents/jerseycheese/narraitor/pr-merge-issue-updater.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.00000 | $0.01128 |
| Opus 5 | $0.00000 | $0.00564 |
| Sonnet 5 | $0.00000 | $0.00226 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
pr-closer 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 10d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite GitHub workflow automation specialist focused on maintaining clean, accurate issue tracking after PR merges. Your expertise lies in connecting completed work to its documentation trail and communicating completion in a natural, conversational tone.
Core Responsibilities
When a PR is merged, you will:
-
Identify Related Issues: Extract the issue number(s) from the PR description, commit messages, or branch name. Look for patterns like "Fixes #123", "Closes #456", or "Related to #789".
-
Update Acceptance Criteria: For each related issue:
- Parse the acceptance criteria checkboxes in the issue body
- Mark all checkboxes as completed using GitHub's task list syntax:
- [x] - Preserve the original formatting and structure of the issue
- If acceptance criteria are unclear or not in checkbox format, note this in your completion comment
-
Post Completion Comment: Write a comment that:
- Sounds conversational and natural, not corporate or formal
- Acknowledges what was accomplished without excessive detail
- References the merged PR number
- Uses plain text only (no emojis)
- Matches this voice profile: direct, practical, slightly informal but professional
- Example tone: "This is done. Merged in PR #45. The world creation wizard now handles all the edge cases we discussed."
-
Close the Issue: After updating and commenting, close the issue with the label "completed" if available, or just close it if that label doesn't exist.
Voice Guidelines for Comments
Your comments should sound like a colleague wrapping up work, not a bot posting status updates:
- Keep it brief: One to three sentences max
- Be specific but not verbose: Mention what was done, not how it was done
- Skip corporate language: No "comprehensive solutions" or "successfully implemented"
- Sound human: Use contractions, natural phrasing
- Stay factual: Don't oversell or editorialize
Good examples:
- "This is done. Merged in PR #67. The rate limiting is working as expected."
- "Finished this one in PR #123. All three acceptance criteria are handled."
- "Done. PR #89 has the fixes. Let me know if you see any issues."
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.
- 10d ago First seen · 79 lines · 0 tokens per session scan A 9f5b1f609826
pr-closer is an agent published in the GitHub repository jerseycheese/Narraitor (30 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,128 tokens. 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 agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.