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 fvadicamo/dev-agent-skills --skill github-pr-creationgit clone --depth 1 https://github.com/fvadicamo/dev-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/fvadicamo/dev-agent-skills/github-pr-creation)<a href="https://agentmods.dev/skills/fvadicamo/dev-agent-skills/github-pr-creation"><img src="https://agentmods.dev/badge/skills/fvadicamo/dev-agent-skills/github-pr-creation/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/fvadicamo/dev-agent-skills/github-pr-creation"><img src="https://agentmods.dev/badge/skills/fvadicamo/dev-agent-skills/github-pr-creation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01496 |
| Opus 5.5 | $0.00030 | $0.00598 |
| Sonnet 5.5 | $0.00015 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
github-pr-creation 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR creation
Creates Pull Requests with task validation, test execution, and Conventional Commits formatting.
Current state
!git rev-parse --abbrev-ref HEAD 2>/dev/null
!git log @{u}..HEAD --oneline 2>/dev/null || echo "(no upstream tracking)"
Core workflow
1. Confirm target branch
ALWAYS ask user before proceeding:
Creating PR from [current-branch] to [target-branch]. Correct?
| Branch flow | Typical target |
|---|---|
| feature/* | develop |
| fix/* | develop |
| hotfix/* | main/master |
| develop | main/master |
2. Search for task documentation
Look for task/spec files that describe what this PR should accomplish. Common locations by tool:
| Tool/Convention | Path |
|---|---|
| Spec2Ship (s2s) | .s2s/plans/*.md (look for active plan matching branch name or commits) |
| AWS Kiro | .kiro/specs/*/tasks.md |
| Cursor | .cursor/rules/*.md, .cursorrules |
| Trae | .trae/rules/*.md |
| GitHub Issues | gh issue list --assignee @me --state open |
| Generic | docs/specs/, specs/, tasks.md, TODO.md |
Extract task IDs, titles, descriptions, and requirements references when found.
3. Analyze commits
For each commit on this branch, identify type, scope, task references, and breaking changes. Map commits to documented tasks when task files exist.
4. Verify task completion
If task documentation exists:
- Identify main task from branch name (e.g.,
feature/task-2-*-> Task 2) - Find all sub-tasks (e.g., Task 2.1, 2.2, 2.3)
- Check which sub-tasks are referenced in commits
- Report missing sub-tasks
If tasks incomplete, STOP and show status:
Task 2 INCOMPLETE: 1/3 sub-tasks missing
- Task 2.1: done
- Task 2.2: done
- Task 2.3: MISSING
Ask user whether to complete missing tasks or proceed anyway.
5. Run tests
Run the project test suite. Tests MUST pass before creating PR.
6. Determine PR type and generate title
| Branch flow | Title prefix |
|---|---|
| feature/* -> develop | feat(scope): |
| fix/* -> develop | fix(scope): |
| hotfix/* -> main | hotfix(scope): |
| develop -> main | release: |
| refactor/* -> develop | refactor(scope): |
| chore/* -> develop | chore(scope): |
| ci/* -> develop | ci(scope): |
| docs/* -> develop | docs(scope): |
What ships with it
1 file 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.
- 1mo ago First seen · 173 lines · 75 tokens per session scan A 23d6a34d738c
github-pr-creation is a skill published in the GitHub repository fvadicamo/dev-agent-skills (72 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,496 once invoked, about $0.0003 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-30.
Other skills, from other repositories
stage
Use when committing work from the current session to stage ONLY hunks the session touched, not the entire file. Prevents accidentally staging unrelated uncommitted changes from other work.
find
Find the local coding-agent session that wrote the uncommitted changes in a file, or in a pasted snippet of changed code or comment text, and give a one-line command that resumes it. Prefers the session that authored the change over a review session. Use when asked which session, chat, thread, or agent made an edit…
gitplan
Plan and execute coherent Conventional Commit groupings for tangled working tree changes — multiple intertwined logical edits that need to be split into separate, reviewable commits.
review-staged
Workflow to review the staged Git diff for verified bugs and then prepare a clean Conventional Commit. Use when the user directly asks to review staged changes or prepare a commit proposal. Do not trigger on a direct commit instruction without a review request.
open-pr
Use this skill to submit the commits on the current branch as one pull request against a GitHub repository. Push the branch, open the PR with an imperative title and a body that names what changed and why, and post a follow-up ping only when CODEOWNERS resolves to one person. One branch per run, one pull request per…
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.