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 agentmods add commands/eddiebelaval/squire/commit-push-prgit clone --depth 1 https://github.com/eddiebelaval/squireWhat 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 | $0.00000 | $0.00602 |
| Opus 5 | $0.00000 | $0.00301 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
commit-push-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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, Push & Create PR
You are executing the commit-push-pr workflow - the most frequently used inner-loop command.
Pre-computed Context (inline bash for speed)
# Current state
BRANCH=$(git branch --show-current)
STATUS=$(git status --porcelain)
STAGED=$(git diff --cached --stat)
UNSTAGED=$(git diff --stat)
REMOTE_STATUS=$(git status -sb | head -1)
RECENT_COMMITS=$(git log --oneline -5)
PR_EXISTS=$(gh pr view --json number 2>/dev/null || echo "none")
Branch: $BRANCH Remote Status: $REMOTE_STATUS Staged Changes: $STAGED Unstaged Changes: $UNSTAGED Recent Commits: $RECENT_COMMITS Existing PR: $PR_EXISTS
User Intent
$ARGUMENTS
Workflow
Step 1: Analyze Changes
- Review STATUS to understand what's changed
- Identify logical groupings if multiple changes exist
- Check if changes are related or should be separate commits
Step 2: Stage Appropriately
- If user specified files, stage those
- If no specification, stage all related changes
- NEVER stage unrelated changes together
Step 3: Craft Commit Message
Follow semantic commit style:
feat:new featurefix:bug fixrefactor:code restructuringdocs:documentationtest:adding testschore:maintenance
Message format:
type: short description (imperative mood)
- Bullet points for details if needed
- Focus on WHY, not WHAT (the diff shows what)
Step 4: Commit & Push
git add [files]
git commit -m "message"
git push -u origin $BRANCH
Step 5: Create or Update PR
If PR_EXISTS is "none":
gh pr create --title "PR Title" --body "## Summary
- Key change 1
- Key change 2
## Test Plan
- [ ] How to verify this works
---
Generated with [Claude Code](https://claude.com/claude-code)"
If PR already exists, just push (PR auto-updates).
Step 6: Report
Output the PR URL and summary of what was done.
Error Handling
- If push fails due to divergence:
git pull --rebase origin $BRANCHfirst - If PR creation fails: check if branch is pushed, check gh auth status
- If nothing to commit: report "No changes to commit"
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.
- 2d ago First seen · 93 lines · 0 tokens per session scan A 3c3ec894bc27
commit-push-pr is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 602 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
deck
Turn a markdown planning doc into a spec-grade 기획서 HTML — a buildless, self-contained document by default, or an on-screen slide presentation when you ask for one. Deterministic md→deck transform + a quality/gap lint; the raw markdown travels with it. Use whenever the user wants a planning document turned into…
regression
Run accumulated regression across scv/archive//TESTS.md (and optionally promote/) with supersede/obsolete skip graph. On failure, triage each slug via AskUserQuestion (regression / obsolete / flaky). Use whenever the user asks whether past features still pass, or before archiving anything — 'run the tests', 'is…
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
handoff
Declare that another repo needs corresponding development: write a handoff (+ decision + conversation) into the workspace root scv repo. Multi-repo (nested) only. Use whenever work in this repo implies a change another repo must make — not only when they type /scv:handoff. Never leave that dependency in prose; this…
status
Show raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.
update
Check installed SCV plugin version vs latest release, and guide the user through /plugin marketplace update + /reload-plugins. Read-only — does not modify project files. (v0.11.2+) Use whenever the user asks whether SCV is current or how to update it — not only when they type /scv:update.