Borrowing it
Nothing to install: this file belongs to adrienm7/ergopti. 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/adrienm7/ergopti/main/.agents/skills/commit-and-push/SKILL.mdgit clone --depth 1 https://github.com/adrienm7/ergoptiWrote 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/adrienm7/ergopti/commit-and-push)<a href="https://agentmods.dev/skills/adrienm7/ergopti/commit-and-push"><img src="https://agentmods.dev/badge/skills/adrienm7/ergopti/commit-and-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/skills/adrienm7/ergopti/commit-and-push"><img src="https://agentmods.dev/badge/skills/adrienm7/ergopti/commit-and-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.00028 | $0.01006 |
| Opus 5.5 | $0.00011 | $0.00402 |
| Sonnet 5.5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
commit-and-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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and push discipline
The rule that matters most
dev and main are release branches. Every push to either one triggers CI
and cuts a release. Pushing without being asked pollutes the release history and
burns CI minutes.
- Commit freely, without asking. Local commits are free and reversible.
- Never squash commits without explicit user authorization in the current conversation. A request to merge, integrate, land, finish, or keep history linear does not authorize squashing. Preserve the atomic commits by default.
- Push to
devormainonly when the user explicitly asks in the current conversation — "push", "tu peux pusher", "merge". - Approval does not carry over. Authorization given for one push covers that push only; the next one needs a new ask.
- Do not infer approval from: a green test suite, a finished fix, a request to "continue", or an earlier instruction to work autonomously. Autonomy covers the work, never the release.
- Leaving several commits stacked locally is the normal, expected end state. Say so plainly: "N commits waiting locally, nothing pushed."
Feature/fix branches that are not dev or main can be pushed freely.
Commit format
Conventional Commits, English, imperative, lowercase, no trailing period, ≤ 72 chars.
<type>(<scope>): <short imperative description>
<body — explain WHY, not WHAT; wrap at 72>
Types: feat fix perf refactor style docs test chore.
Breaking change: feat!: plus an explanation in the body.
- One commit per fix. Do not batch unrelated fixes; each must be revertable alone.
- The body is for motivation and root cause — the diff already shows the what.
Forcing the next stable version
A push to main numbers its tag from the subjects since the last stable tag:
feat bumps the minor, !: or BREAKING: the major, anything else the patch.
When the maintainer asks for a specific version, add this line on its own in
a commit message after the last stable tag (the newest such commit wins):
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.
- 8d ago Changed · +17 lines 51a5c7c3aaf2
- 15d ago First seen · 80 lines · 28 tokens per session scan A 7714c986d753
commit-and-push is a skill published in the GitHub repository adrienm7/ergopti (14 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,006 once invoked, about $0.0001 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-10-14.
Other skills, from other repositories
github-pr-workflow
GitHub issues and PR lifecycle: file/triage issues, carry an issue to a verified PR, branch, commit, open, CI, merge.
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
gitlab-issue-to-mr
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
dependabot-consolidator
Consolidate a repository's open Dependabot PRs into one tested branch and PR, grouping by ecosystem and risk, verifying with baseline-diff gates, and closing out on operator approval. Use when a repo has multiple open Dependabot PRs to batch, when consolidating dependency bumps into a single reviewable PR, or when…
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
commit
Delegate a single Conventional Commit.