Borrowing it
Nothing to install: this file belongs to dork-labs/dorkos. 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/dork-labs/dorkos/main/.claude/commands/git/push.mdgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/push)<a href="https://agentmods.dev/commands/dork-labs/dorkos/push"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/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/dork-labs/dorkos/push"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/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.00012 | $0.00619 |
| Opus 5.5 | $0.00005 | $0.00248 |
| Sonnet 5.5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Push
Push commits to remote after validating that there are no lint, type, or build errors.
Task
Step 1: Check Current State
Verify there are commits to push:
# Check if branch has upstream
git status
# Show unpushed commits
git log @{u}..HEAD --oneline 2>/dev/null || git log --oneline -5
If there are no commits to push, report this and stop.
Step 2: Run Validation Checks
Run all validation checks. All must pass before pushing.
pnpm lint
pnpm typecheck
pnpm build
If any check fails: Stop and report the errors. Do not push.
Step 2.5: Verification Gate
After all checks pass, verify with fresh evidence:
- Re-read the output of lint, typecheck, and build
- Confirm zero errors in each
- Do not push based on a previous run — the checks in Step 2 ARE the fresh evidence
Refer to the verification-before-completion skill.
Step 3: Review What Will Be Pushed
Show the commits that will be pushed:
# Show commits ahead of remote
git log @{u}..HEAD --oneline 2>/dev/null || echo "No upstream branch set"
# Show current branch
git branch --show-current
Step 4: Push to Remote
Push the current branch:
git push
If no upstream is set, push with -u flag:
git push -u origin $(git branch --show-current)
Step 5: Verify
Confirm the push was successful:
git status
Output Format
Git Push
Validation:
[x] Lint passed
[x] Typecheck passed
[x] Build passed
Pushed:
Branch: [branch-name]
Commits: X commit(s)
- [hash] [message]
- [hash] [message]
Status: Successfully pushed to origin
Edge Cases
- Lint fails: Report errors, suggest fixes, do not push
- Typecheck fails: Report errors with file locations, do not push
- Build fails: Report build errors, do not push
- No upstream: Set upstream with
-u origin <branch> - Remote rejected: Report rejection reason (likely needs pull/rebase)
- No commits to push: Report "Already up to date with remote"
- Uncommitted changes: Warn user about uncommitted changes (but still push existing commits)
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 · 118 lines · 12 tokens per session scan A 16267c31b65f
push is a command published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 619 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
commit-all
Stage and commit all current changes with a single message. Auto Git Push will pick up and push to origin within 30s.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
commit
Based on the above changes, create a single git commit.
commit-push-pr
Commit, push, and open a PR.
sp.git.commit_pr
An autonomous Git agent that intelligently executes git workflows. Your task is to intelligently executes git workflows to commit the work and create PR.
caveman-commit
Generate a terse caveman-style commit message for staged changes.