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 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/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/dmythro/agent-skills/git-pr"><img src="https://agentmods.dev/badge/skills/dmythro/agent-skills/git-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 87 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 379 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00138 | $0.07619 |
| Opus 5.5 | $0.00055 | $0.03048 |
| Sonnet 5.5 | $0.00028 | $0.01524 |
| Haiku 4.5 | $0.00014 | $0.00762 |
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 9d 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 — 387 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.
Verified against gh v2.102.0 (2026-09-30): every gh subcommand and flag used here, against its --help. glab: not verified -- no pinned version yet; check glab <cmd> --help before relying on a glab flag. If gh --version is newer, read the release notes since v2.102.0 before relying on flag details. The CodeRabbit CLI pin lives in the coderabbit skill.
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) |
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.
- 9d ago Changed · +4 lines 2223097f999d
- 19d ago Changed · +2 lines 775184f99a85
- 27d ago Changed 100d7a2760ef
- 1mo ago Changed · +1 lines bd48a94d9fa1
- 1mo ago Changed 88298f262434
- 1mo 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 (7 stars, last pushed 10d ago), licensed MIT. It adds 138 tokens to every session and 7,619 once invoked, about $0.0006 per session on Opus 5.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
commit-message-expert
Generates consistent, meaningful Git commit messages based on a diff or description of changes. Use when writing or reviewing a commit message, especially to follow Conventional Commits or a project's existing convention.
secrets-scanner
Narrowly scans code and config for hardcoded secrets, credentials, API keys, and tokens. Use before a commit/PR, or when auditing a codebase for accidentally-committed secrets.
changelog-generator
Converts commits or development updates into clean, categorized release notes and changelogs. Use when preparing a release and raw commit history needs to become human-readable notes.
git-conflict-resolver
Resolves complex git rebase and merge conflicts with AST-level context, preserving intent across concurrent branches.
git-hook-automation-designer
Configures pre-commit and pre-push hooks (Husky, Lefthook) for fast lint-staged, branch naming, and secret blocking.
contributor-guide-writer
Creates clear, welcoming CONTRIBUTING.md files, PR templates, and local dev onboarding guides for open source projects.