Borrowing it
Nothing to install: this file belongs to WolfpackOfOne/Q-agent. 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/WolfpackOfOne/Q-agent/main/.claude/skills/push-git/SKILL.mdgit clone --depth 1 https://github.com/WolfpackOfOne/Q-agentWrote 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/skills/wolfpackofone/q-agent/push-git)<a href="https://agentmods.dev/skills/wolfpackofone/q-agent/push-git"><img src="https://agentmods.dev/badge/skills/wolfpackofone/q-agent/push-git/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/skills/wolfpackofone/q-agent/push-git"><img src="https://agentmods.dev/badge/skills/wolfpackofone/q-agent/push-git.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.00046 | $0.00770 |
| Opus 5.5 | $0.00018 | $0.00308 |
| Sonnet 5.5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
push-git 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 2mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push Git Skill
Commit all pending changes and push to Git/GitHub.
Usage
/push-git [commit message]
Examples:
/push-git— auto-generates commit message from changes/push-git "Add yfinance pipeline"— uses provided message
Workflow
1. Inspect Current State
git status --short
git remote -v
git branch --show-current
git log --oneline -5
Review what will be committed. Summarize the changes for the user.
2. Check for Marimo Notebooks
Scan all staged and modified .py files for marimo notebooks:
# For each changed .py file, check if it's a marimo notebook
head -20 "<file>" | grep -q 'marimo.App'
If any marimo notebooks are found among the changed files, ask the user:
Found marimo notebooks in changed files:
<path/to/notebook.py>Would you like to render them to
.ipynbfor GitHub viewing? (This runsmarimo exportwith outputs.)
If the user says yes, export each notebook:
infrastructure/marimo/venv/bin/marimo export ipynb "<notebook.py>" -o "<notebook.ipynb>" --include-outputs
Then stage the generated .ipynb files alongside the other changes.
If the user says no, skip rendering and proceed with the commit.
3. Stage Changes
Stage all relevant files. Use specific file paths rather than git add -A when possible.
Do NOT stage:
.env, credentials, secretsconfig.jsonfilesbacktests/,__pycache__/,.ipynb_checkpoints/- Files in
.gitignore
If there are many files, group them logically and stage by directory or pattern.
4. Commit
If a commit message was provided as an argument, use it. Otherwise, generate a concise commit message based on the changes.
For large changesets, consider asking the user whether to split into multiple commits or do one big commit.
5. Push to GitHub
git push origin <current-branch>
Do not force-push unless the user explicitly asks.
6. Report Results
Commit: <short hash> <message>
Push: origin/<branch> — success / failed
Notebooks rendered: <list> / none
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.
- 2mo ago First seen · 115 lines · 46 tokens per session scan A 736ad4ab6eeb
push-git is a skill published in the GitHub repository WolfpackOfOne/Q-agent (5 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 770 once invoked, about $0.0002 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.