Borrowing it
Nothing to install: this file belongs to nyatinte/ccexp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nyatinte/ccexp/main/.claude/commands/draft-pr.mdgit clone --depth 1 https://github.com/nyatinte/ccexpWrote 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/commands/nyatinte/ccexp/draft-pr)<a href="https://agentmods.dev/commands/nyatinte/ccexp/draft-pr"><img src="https://agentmods.dev/badge/commands/nyatinte/ccexp/draft-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/commands/nyatinte/ccexp/draft-pr"><img src="https://agentmods.dev/badge/commands/nyatinte/ccexp/draft-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.00009 | $0.00581 |
| Opus 5.5 | $0.00004 | $0.00232 |
| Sonnet 5.5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
draft-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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft PR content with the following additional instructions: $ARGUMENTS
Context
- Current branch:
!git branch --show-current - Remote tracking:
!git status -sb - Recent commits on this branch:
!git log origin/main..HEAD --oneline - Repository info:
!gh repo view --json owner,name
Your task
Create a PR draft in PR.md file based on the current branch changes.
Steps
-
Verify branch status:
- Ensure current branch is not main/master
- Check if there are commits to create PR for
- If no commits or on main branch, inform user and exit
-
Check for existing PR:
- Check if PR already exists:
gh pr list --head $(git branch --show-current) - If PR exists, get current PR details for comparison
- Check if PR already exists:
-
Analyze repository PR style:
- Search for past PRs:
gh pr list --state merged --limit 10 - Analyze recent PRs for:
- Title format and language
- Description structure
- Common patterns
- Search for past PRs:
-
Load PR template:
- Read
.github/PULL_REQUEST_TEMPLATE.mdif it exists - Use template structure as base
- Read
-
Analyze changes:
- Get all commit messages:
git log origin/main..HEAD --pretty=format:"%s" - Get detailed diff if needed:
git diff origin/main..HEAD --stat - Understand the overall purpose of changes
- Get all commit messages:
-
Create PR.md file:
- Follow the template structure (Summary, Why, Changes with AS-IS/TO-BE)
- Write clear title (first line)
- Write comprehensive description (rest of file)
- Match the repository's PR language and style
- Include all relevant context
-
Show draft to user:
- Display the created
PR.mdcontent - Inform user they can edit
PR.mdbefore creating the PR - Suggest using
/create-prcommand next
- Display the created
Important Notes
- DO NOT create the actual PR - only draft the content in PR.md
- Follow the repository's existing PR style and language
- Ensure PR.md follows the template format (Summary/Why/Changes)
- Make the description comprehensive but concise
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 · 66 lines · 9 tokens per session scan A f311cd92e824
draft-pr is a command published in the GitHub repository nyatinte/ccexp (270 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 581 once invoked, about $0.0000 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 commands, from other repositories
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-tag
Create and push a version tag after a release PR has been merged.