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/dmythro/agent-skills/git-prnpx skills add dmythro/agent-skills --skill git-prgit clone --depth 1 https://github.com/dmythro/agent-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/dmythro/agent-skills/git-pr)<a href="https://agentmods.dev/skills/dmythro/agent-skills/git-pr"><img src="https://agentmods.dev/badge/skills/dmythro/agent-skills/git-pr.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 | $0.00138 | $0.06926 |
| Opus 5 | $0.00069 | $0.03463 |
| Sonnet 5 | $0.00028 | $0.01385 |
| Haiku 4.5 | $0.00014 | $0.00693 |
Grade A, and why
git-pr 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 today.
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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR and MR Workflows
Primary skill for pull request and merge request workflows across GitHub and GitLab. Covers the full lifecycle: creation, review queries, comment handling, line-specific comments, and merging. All recipes use minimal field sets for token efficiency.
Context Check (Do This First)
Before starting any PR workflow, detect the current state. This determines the right action:
# Check if a PR exists for the current branch (allowlisted, zero approval)
gh pr view --json number,state,reviewDecision,reviewRequests,title 2>/dev/null
| Result | Next action |
|---|---|
PR exists, CHANGES_REQUESTED |
Fetch unresolved threads (see Review Comment Handling) |
PR exists, REVIEW_REQUIRED or has pending reviewRequests |
Check review state or wait for reviewers |
PR exists, a bot pending in REST requested_reviewers (Copilot shows as Copilot) |
Auto-review in flight -- wait for it (Bot Review Loop); do NOT re-request |
| PR exists, unresolved review comments | Address the comments first (Review Comment Handling); never request a new review over outstanding ones |
PR exists, APPROVED |
Check CI status or proceed with merge |
| PR exists, no review decision yet | Check CI status, review state, or push more changes |
| No PR for current branch | Create a PR (see PR/MR Creation) |
This avoids offering to create a PR when one already exists, and immediately surfaces pending review work. The reviewDecision field reliably indicates whether a reviewer has requested changes without needing to fetch individual threads.
Auto-review is an optional setting -- never assume it either way (GitHub): automatic Copilot code review comes from either a repo/org ruleset or the author's personal Copilot setting, so its presence varies between accounts, orgs, and even repos of the same owner. When enabled it requests Copilot on every non-draft PR at creation (and when a draft is marked ready for review), so a freshly created PR may already have a pending bot request or bot comments minutes later -- and on other repos nothing fires at all. The ruleset source is detectable read-only (the copilot_code_review rule via gh api repos/{owner}/{repo}/rules/branches/{branch}; see references/copilot-review-config.md), but the personal setting has no API -- so an empty ruleset check still means detect, don't assume: check for a pending request or an existing bot review first, and only request one if neither shows up; otherwise you get a duplicate round. Gotcha: the pending bot request is only visible via gh api repos/{owner}/{repo}/pulls/{n}/requested_reviewers (login Copilot) -- gh pr view --json reviewRequests omits bot reviewers and stays empty.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed 88298f262434
- 4d ago First seen · 380 lines · 138 tokens per session scan A 2aa729871e62
git-pr is a skill published in the GitHub repository dmythro/agent-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 138 tokens to every session and 6,926 once invoked, about $0.0007 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
security-auditor
Analyzes code and implementations for common security weaknesses and unsafe practices - injection, auth flaws, secrets handling, unsafe deserialization, and access control. Use before shipping anything handling user input, auth, or sensitive data.
compliance-privacy-reviewer
Reviews how a feature or system handles PII, data retention, and consent against common privacy-framework principles (GDPR-style). Use when a feature collects, stores, or processes personal data - not a substitute for legal advice.
adr-writer
Writes an Architecture Decision Record (ADR) documenting a decision, its context, the options considered, and its consequences. Use to record a decision that's already been made so future readers understand why.
architecture-reviewer
Reviews application architecture for scalability, coupling, separation-of-concerns, and maintainability issues. Use for system-level review, not individual file/function-level code review.
migration-planner
Plans a safe, incremental migration (framework, database, service, or platform) with rollback points and a dual-running strategy. Use when replacing something that's already in production and can't just be swapped in one step.
project-planner
Converts an idea into a structured development plan with milestones, tasks, dependencies, and implementation phases. Use when an idea or feature needs to be broken into a plan before work starts.