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 mir-am/skills-agents-ai-coding --skill gh-prgit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/gh-pr)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/gh-pr"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-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/mir-am/skills-agents-ai-coding/gh-pr"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-pr.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.00016 | $0.02090 |
| Opus 5.5 | $0.00006 | $0.00836 |
| Sonnet 5.5 | $0.00003 | $0.00418 |
| Haiku 4.5 | $0.00002 | $0.00209 |
Grade A, and why
gh-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 5d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Validate feature branch has commits ahead of master/main
- Push branch to remote if needed
- Generate PR title summarizing all commits + session work (no type prefix)
- Create concise PR description with summary and 3-5 key changes
- Link GitHub issue if working on one in current session
- Create GitHub PR using
ghCLI and self-assign it to the authenticated GitHub user - Update root
CHANGELOG.mdwhen present with one PR-linked unreleased bullet using the PR URL, then commit and push that changelog update back to the same branch
When to use me
Use this skill when the user asks to create a GitHub pull request from the current feature branch.
Prerequisites
- Must be on a feature branch (not master/main)
- Branch must have commits ahead of base branch
- GitHub CLI (
gh) must be installed and authenticated - If
ghnot installed → error: "GitHub CLI not found. Install: https://cli.github.com/"
Validation Workflow
- Check current branch:
git branch --show-current - If on
masterormain→ error message and exit - Check for commits ahead of base:
- Try:
git log master..HEAD --oneline - Fallback:
git log main..HEAD --oneline
- Try:
- If no commits ahead → warn user and exit
Push Workflow
- Check if branch exists on remote:
git ls-remote --heads origin <branch-name> - If not on remote:
git push -u origin <branch-name> - If exists on remote:
git push - If a follow-up changelog sync creates a new
CHANGELOG.mdcommit after PR creation, push that commit to the same branch as well
PR Title Generation
- Analyze all commit messages in the branch
- Analyze agent's session context and work completed
- Summarize into one cohesive title (no type prefix)
- If commits use conventional format (
feat:,fix:), strip type prefixes - Capitalize first letter
- Examples:
Add CSV export functionality and update documentationResolve NPE in call graph builderImplement parallel test execution
PR Description Generation
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.
- 5d ago First seen · 202 lines · 16 tokens per session scan A ca4655c69bd3
gh-pr is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 2,090 once invoked, about $0.0001 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-10-02.
Other skills, from other repositories
git-workflow
Conventional commits, PR creation, and quality gate verification.
review-gate
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.