Borrowing it
Nothing to install: this file belongs to jayminwest/kotadb. 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/jayminwest/kotadb/develop/.claude/commands/git/pull_request.mdgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/pull_request)<a href="https://agentmods.dev/commands/jayminwest/kotadb/pull_request"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/pull_request/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/jayminwest/kotadb/pull_request"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/pull_request.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.00000 | $0.01629 |
| Opus 5.5 | $0.00000 | $0.00652 |
| Sonnet 5.5 | $0.00000 | $0.00326 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
pull_request 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pull_request
Template Category: Path Resolution
Open a GitHub pull request as soon as implementation work is complete and validated.
Variables
- branch_name: $1
- issue_json: $2
- plan_file: $3 (relative path within
.claude/.cache/specs/) - adw_id: $4
CRITICAL: Output Format Requirements
Return ONLY the PR URL as plain text on a single line.
DO NOT include:
- Explanatory text (e.g., "Successfully created pull request!", "The PR is ready for review")
- Markdown formatting (no bold, no
``` blocks) - Multiple lines or additional commentary
- PR metadata (title, description, etc.)
Correct output:
https://github.com/user/kota-db-ts/pull/123
INCORRECT output (do NOT do this):
Successfully created pull request!
PR URL: https://github.com/user/kota-db-ts/pull/123
The pull request is now ready for review. It includes validation evidence and anti-mock compliance notes.
**Pull Request Created**
https://github.com/user/kota-db-ts/pull/123
Preconditions
- Working tree is clean (
git status --shortempty) and the current branch matches<branch_name>. - All commits for the issue exist locally and remotely (
feat/,bug/,chore/, etc. →develop→main). - Commit messages validated: All commit messages follow Conventional Commits format (verified by validation system)
- Staged files verified: All files mentioned in plan are properly staged (verified by validation system)
- Level 2 or higher validation from
/validate-implementationhas been rerun with passing results captured for the PR body. - Anti-mock evidence is ready: note which real-service suites ran, data seeded, and any temporary skips with follow-up issues.
- Plan document and issue references are up to date with final status and validation notes.
Preparation Checklist
git branch --show-current– verify you are on<branch_name>.git fetch --all --prune– make sure remotes are current.git status --short– confirm no unstaged or untracked files remain.git log origin/develop..HEAD --oneline– review commits that will ship.- Verify commit messages: Review commit messages with
git log --onelineto ensure Conventional Commits format - Verify PR description: Ensure validation evidence section is complete with actual command output
gh pr status– ensure the branch does not already have an open PR.- Re-run the selected validation level; fix issues immediately before continuing.
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 · 141 lines · 0 tokens per session scan A 5c398bf1c9d3
pull_request is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,629 tokens. 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
commit
When you receive this command, do the following.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
fest-commit
Commit changes with festival traceability metadata.
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.
sandbox-promote
Promote an accepted, version-worthy WIP artifact from .credo/sandbox-tmp/ / to .credo/sandbox/ /. is the sandbox-tmp folder name (argument: $1).