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/sequenzia/claude-plugins/git-pushgit clone --depth 1 https://github.com/sequenzia/claude-pluginsWhat 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.00010 | $0.00621 |
| Opus 5 | $0.00005 | $0.00311 |
| Sonnet 5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
git-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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Push
Push local commits to the remote repository. Automatically handles upstream conflicts by rebasing and retrying.
Workflow
Execute these steps in order.
Step 1: Check for Commits to Push
Get the current branch and check if there are commits to push:
git branch --show-current
git rev-parse HEAD
git rev-parse @{u} 2>/dev/null || echo "no-upstream"
- If no upstream exists, continue to push (will set upstream).
- If local HEAD equals upstream HEAD, report: "Already up to date. Nothing to push." and stop.
- If local is ahead of upstream, continue to Step 2.
Step 2: Push to Remote
Push the current branch to origin:
git push origin <current-branch>
- On success, continue to Step 4.
- On failure, continue to Step 3.
Step 3: Handle Push Failure
If push fails due to upstream changes:
-
Pull with rebase:
git pull --rebase origin <current-branch> -
If rebase succeeds, retry push:
git push origin <current-branch> -
If rebase has conflicts:
- Report: "Rebase conflicts detected. Please resolve conflicts manually."
- List the conflicting files
- Provide instructions:
To resolve: 1. Fix conflicts in the listed files 2. Run: git add <resolved-files> 3. Run: git rebase --continue 4. Run: git push origin <branch> To abort: Run: git rebase --abort - Stop workflow.
Step 4: Report Success
On successful push, report:
Pushed to origin/<branch>
Show the commits that were pushed:
git log @{u}..HEAD --oneline 2>/dev/null || git log -1 --oneline
Error Recovery
Push rejected (upstream changes):
- The workflow automatically attempts
git pull --rebaseand retries once - If conflicts occur, resolve manually following the provided instructions
Rebase conflicts:
- Resolve conflicts in listed files
git add <resolved-files>for eachgit rebase --continueto finishgit push origin <branch>to push
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 · 119 lines · 10 tokens per session scan A c23579335226
git-push is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 621 once invoked, about $0.0001 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.