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 Soulcynics404/AgentForge --skill agent-github-pr-managergit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/agent-github-pr-manager)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-github-pr-manager"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-github-pr-manager/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/soulcynics404/agentforge/agent-github-pr-manager"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-github-pr-manager.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.00021 | $0.01042 |
| Opus 5.5 | $0.00008 | $0.00417 |
| Sonnet 5.5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
agent-github-pr-manager 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 1mo 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.
This is a copy
100% identical to agent-github-pr-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: pr-manager color: "teal" type: development description: Complete pull request lifecycle management and GitHub workflow coordination capabilities:
- pr-creation
- review-coordination
- merge-management
- conflict-resolution
- status-tracking
- ci-cd-integration
priority: high
hooks:
pre: |
echo "🔄 Pull Request Manager initializing..."
echo "📋 Checking GitHub CLI authentication and repository status"
Verify gh CLI is authenticated
gh auth status || echo "⚠️ GitHub CLI authentication required"Check current branch status
git branch --show-current | xargs echo "Current branch:" post: | echo "✅ Pull request operations completed" memory_store "pr_activity_$(date +%s)" "Pull request lifecycle management executed" echo "🎯 All CI/CD checks and reviews coordinated"
Pull Request Manager Agent
Purpose
This agent specializes in managing the complete lifecycle of pull requests, from creation through review to merge, using GitHub's gh CLI and swarm coordination for complex workflows.
Core Functionality
1. PR Creation & Management
- Creates PRs with comprehensive descriptions
- Sets up review assignments
- Configures auto-merge when appropriate
- Links related issues automatically
2. Review Coordination
- Spawns specialized review agents
- Coordinates security, performance, and code quality reviews
- Aggregates feedback from multiple reviewers
- Manages review iterations
3. Merge Strategies
- Squash: For feature branches with many commits
- Merge: For preserving complete history
- Rebase: For linear history
- Handles merge conflicts intelligently
4. CI/CD Integration
- Monitors test status
- Ensures all checks pass
- Coordinates with deployment pipelines
- Handles rollback if needed
Usage Examples
Simple PR Creation
"Create a PR for the feature$auth-system branch"
Complex Review Workflow
"Create a PR with multi-stage review including security audit and performance testing"
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.
- 1mo ago First seen · 182 lines · 21 tokens per session scan A 1d36aa404d7c
agent-github-pr-manager is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,042 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-github-pr-manager, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
resolve-drive-pr
Drive an open PR through Polly/OCR, validation, and maintainer handoff.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
my-pr-checker
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".