Borrowing it
Nothing to install: this file belongs to sanmak/specops. 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/sanmak/specops/main/.claude/commands/push.mdgit clone --depth 1 https://github.com/sanmak/specopsWrote 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/sanmak/specops/push)<a href="https://agentmods.dev/commands/sanmak/specops/push"><img src="https://agentmods.dev/badge/commands/sanmak/specops/push/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/sanmak/specops/push"><img src="https://agentmods.dev/badge/commands/sanmak/specops/push.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.00554 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
push 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push the current branch to remote after validating all pre-push checks pass.
Instructions
Follow these steps precisely.
Step 1: Check current state
Run git status to confirm the working tree. If there are uncommitted changes (modified or untracked files), warn the user: "There are uncommitted changes. Run /commit first or commit manually before pushing." and stop.
Step 2: Check if there is anything to push
Run git log @{upstream}..HEAD --oneline 2>/dev/null to see unpushed commits.
If the command fails (no upstream set), note that we will push with -u to set upstream tracking.
If there are no unpushed commits and upstream exists, inform the user "Already up to date with remote -- nothing to push" and stop.
Step 3: Run pre-push validation
Before pushing, proactively run the same checks the pre-push hook will run, so we can fix issues before they block the push:
python3 generator/validate.py-- platform validationshasum -a 256 -c CHECKSUMS.sha256-- checksum verificationpython3 generator/generate.py --all && git diff --exit-code platforms/ skills/ .claude-plugin/-- generated files freshnesspython3 tests/check_schema_sync.py-- schema structurebash scripts/run-tests.sh-- full test suitenpx markdownlint-cli2 "core/**/*.md" "docs/**/*.md" ".claude/commands/**/*.md" "README.md" "CLAUDE.md" "QUICKSTART.md" "CONTRIBUTING.md" "CHANGELOG.md"-- markdown lint (skip if npx not available)
If any check fails:
- Report which check failed and the error output
- If the failure is fixable (stale generated files, stale checksums), explain what the user needs to do
- Do NOT push. Stop and let the user fix the issue.
Step 4: Push
Determine the current branch: git rev-parse --abbrev-ref HEAD
If the branch has an upstream, run:
git push
If the branch does not have an upstream, run:
git push -u origin <branch-name>
Do NOT use --no-verify -- let the pre-push hook run normally.
If the push fails, report the error to the user.
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 · 59 lines · 0 tokens per session scan A 22b144da2557
push is a command published in the GitHub repository sanmak/specops (49 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 554 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
skill-creator
Create or update an OpenCode skill using the bundled skill-creator workflow.
skill-registry
Rebuild the OpenCode skill registry for the current project and installed skills.
taskstoissues
A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…
approve-proposed
Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…
explain
/explain Explain the last agent action (quick mode) /explain --verbose Full trace with file changes and decision rationale /explain --story STORY-XXX All actions for a story in chronological order /explain --agent Last action by a specific agent /explain --session All actions from a specific session /explain --diff…