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.
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/pr)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/pr"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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/khaledsaeed18/dotclaude/pr"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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.00089 | $0.00738 |
| Opus 5.5 | $0.00036 | $0.00295 |
| Sonnet 5.5 | $0.00018 | $0.00148 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
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 24d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Options: $ARGUMENTS
Branch, upstream, and default base:
!git branch --show-current 2>/dev/null; git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "(no upstream)"; gh repo view --json defaultBranchRef --jq .defaultBranchRef.name 2>/dev/null
Uncommitted:
!git status --short 2>/dev/null | head -20
Commits on this branch:
!git log --oneline $(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main 2>/dev/null)..HEAD 2>/dev/null
Existing PR for this branch:
!gh pr view --json number,url,state 2>/dev/null || echo "(none)"
Task
- Refuse on a protected branch. If the current branch is the default branch (or
main/master/develop), stop and ask for a feature branch; do not create one silently. - If a PR already exists, print its URL and offer to update the body instead of creating a duplicate.
- Uncommitted changes: if any, ask whether to commit them first. If yes, apply the
git-commitskill for one commit (explicit staging, repo rules, no AI mentions). If no, proceed with what is committed and say the working tree still has changes. - Push with
git push -u origin <branch>after confirming the branch and remote. A rejected push (non-fast-forward) is reported, never forced. - Write the PR with the
pr-descriptionskill fromgit diff <base>...HEADand the commit messages: a title under 70 characters in the repo's convention, and a body with what changed, why, risk, and how it was tested. If a PR template exists (.github/pull_request_template.md), fill its sections instead. If the arguments include an issue number, addCloses #<n>. - Show the title, body, base, and draft status, then ask for a yes before
gh pr create --base <base> --title ... --body-file ...(--draftwhen asked). Base defaults to the repo's default branch. - Report the PR URL. Do not enable auto-merge, request reviewers, or add labels unless asked.
Inspired by
The role and scope follow the commit-commands plugin's /commit-push-pr command in Anthropic's claude-code repository. That repository is not open-licensed, so nothing is copied from it; every line here was written for this registry.
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.
- 24d ago First seen · 42 lines · 89 tokens per session scan A 38f06f6609f7
pr is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 738 once invoked, about $0.0004 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-09-22.
Other commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
commit
Create a commit with validation (lint + tests) — optionally pass the message.
done
Finalize changes — quick review + check + commit.
push
Send commits to the remote.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.