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/blendsdk/claude-codeops/gitcmpgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00040 | $0.00714 |
| Opus 5 | $0.00020 | $0.00357 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
gitcmp 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitcmp — commit, rebase, and push
Run the full /gitcm flow, then sync with the remote and push.
Current state
- Status: !
git status --short - Branch & upstream: !
git status -sb | head -1
Steps
- Do everything
/gitcmdoes: clean-tree guard ("nothing to commit" → stop) → verify (build + test) → deliberate staging → file-based Conventional Commit → pre-commit-hook handling → clean up. Never usegit commit -m. If verify fails, stop and report. - Upstream check. If the branch has no upstream (
git rev-parse --abbrev-ref @{u}fails — a first push of a new branch), skip the rebase and, after confirming with the user, push withgit push -u origin HEAD. Then report and stop here. - Rebase on the remote:
git pull --rebase. - If the rebase is clean, push:
git push. Then report the pushed commit. - If the rebase reports conflicts, follow the Conflict Protocol below — do not push.
If the user passed $ARGUMENTS, use it as a hint for the scope or emphasis. See /gitcm for
the full commit-message format and scope guidance.
Conflict Protocol (on git pull --rebase conflicts)
- STOP. Do not attempt automatic conflict resolution.
- Report the conflicting files and the nature of each conflict.
- Ask the user how to proceed:
- Abort the rebase and keep the local commit (
git rebase --abort) - "I'll resolve manually — show me the conflicts"
- Abort and discard the commit (rare)
- Abort the rebase and keep the local commit (
- Wait for the user's decision before doing anything.
- After resolution, re-run the project verify command before pushing.
Never accept "theirs"/"ours" wholesale, never force-push, and never reset/delete commits without explicit user instruction.
Push Failure Recovery
| Failure | Likely cause | Recovery |
|---|---|---|
| Authentication error | SSH key / token | Report — cannot fix programmatically |
| Remote rejection | Branch protection | Report — may need a PR workflow |
| Non-fast-forward | Remote has new commits | git pull --rebase, resolve, retry push once |
| No upstream configured | First push of a new branch | Confirm, then git push -u origin HEAD |
| Network error | Connectivity | Wait briefly, retry once, then report |
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.
- yesterday First seen · 59 lines · 40 tokens per session scan A 50f4f722b57a
gitcmp is a command published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 714 once invoked, about $0.0002 per session on Opus 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.