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 skills add d-gangz/dgang-skills --skill commit-pushgit clone --depth 1 https://github.com/d-gangz/dgang-skillsWrote 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/d-gangz/dgang-skills/commit-push)<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/commit-push"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/commit-push.svg" alt="Measured on agentmods" 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.00015 | $0.00348 |
| Opus 5 | $0.00008 | $0.00174 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
commit-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 7d 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.
What it actually says
Generate organized commits & push changes
Goal: Commits are the retrieval index for future sessions — batch and word them so a later git log reads as a useful changelog of what changed and why.
Pre-fetched context
Current branch: !git branch --show-current
Working tree status:
!`git status --porcelain`
Change summary (staged + unstaged):
!`git diff HEAD --stat`
Steps
-
Review the context above:
- If on main/master, warn me but still continue.
- If there are no changes at all (staged or unstaged), inform me and stop.
- If there are already staged changes: unstage them with
git reset HEADand explain "Unstaging to create organized batched commits", then proceed with all unstaged changes. - If you don't recognize a change from this session's context, read its diff before batching.
-
Batch the changes into atomic, focused commits. If changes relate to a Linear issue mentioned in conversation, include its magic word (ref) + ID in that commit (e.g.,
feat(auth): add login, ref INT-42). -
Create the commits (proceed immediately, no approval needed). For each batch,
git addonly that batch's files — nevergit add .or-A. -
Push to the current branch and confirm success.
-
Report back to user: commits created (message, files), batching rationale, push status.
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.
- 7d ago First seen · 39 lines · 15 tokens per session scan A 4ffe83efbd1a
commit-push is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 348 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…