Borrowing it
Nothing to install: this file belongs to kimrejstrom/alpacalyzer-algo-trader. 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/kimrejstrom/alpacalyzer-algo-trader/main/.agents/commands/create-pr.mdgit clone --depth 1 https://github.com/kimrejstrom/alpacalyzer-algo-traderWrote 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/kimrejstrom/alpacalyzer-algo-trader/create-pr)<a href="https://agentmods.dev/commands/kimrejstrom/alpacalyzer-algo-trader/create-pr"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/create-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/kimrejstrom/alpacalyzer-algo-trader/create-pr"><img src="https://agentmods.dev/badge/commands/kimrejstrom/alpacalyzer-algo-trader/create-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.00000 | $0.00439 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
create-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 10d 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.
What it actually says
Create PR Command
Create a pull request after completing feature work.
Usage
/create-pr
Argument Indexing
- Claude Code: No arguments needed
- OpenCode: No arguments needed
Steps
1. Run Tests
uv run pytest tests -x -q
2. Run Linting
uv run ruff check .
uv run ruff format .
3. Run Type Checking
uv run ty check src
4. Get Repo Info
git remote get-url origin
Parse owner and repo name.
5. Check Changes
git status
git diff --cached
6. Commit if Needed
If there are uncommitted changes:
git add -A
git commit -m "feat(scope): description for #XX"
7. Push Branch
git push -u origin feature/issue-XX-description
8. Create PR
Use gh CLI:
gh pr create --repo <owner>/<repo> \
--title "feat(scope): description for #XX" \
--head feature/issue-XX-description \
--base main \
--body-file - <<'EOF'
## Summary
<description>
## Issue
Closes #XX
EOF
9. Trigger Code Review
@code-reviewer Please review:
- ISSUE_NUMBER: <issue_number>
- PR_NUMBER: <pr_number>
- OWNER: <owner>
- REPO: <repo>
- FEATURE_DESCRIPTION: <brief description>
10. Report Completion
Reply to user:
Feature #XX ready for review. PR url: {PR_URL}, also see docs/plans/_PLAN_issue-XX.md for details
Notes
- Ensure all tests pass before creating PR
- Include issue number in commit message and PR title
- Always trigger code review (mandatory)
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.
- 10d ago First seen · 109 lines · 0 tokens per session scan A 83c011577b5d
create-pr is a command published in the GitHub repository kimrejstrom/alpacalyzer-algo-trader (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 439 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.