Borrowing it
Nothing to install: this file belongs to justomsharma/github-resume-assistant. 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/justomsharma/github-resume-assistant/main/.claude/skills/commit-push/SKILL.mdgit clone --depth 1 https://github.com/justomsharma/github-resume-assistantWrote 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/justomsharma/github-resume-assistant/commit-push)<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/commit-push"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/commit-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/justomsharma/github-resume-assistant/commit-push"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/commit-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.00049 | $0.00433 |
| Opus 5.5 | $0.00020 | $0.00173 |
| Sonnet 5.5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
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 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.
What it actually says
commit-push
Commit and push the reviewed changes. Follow docs/GIT_WORKFLOW.md.
Gate — requires explicit user go-ahead
Do NOT run this skill (or /open-pr, /review-pr, or merge) on your own after
tests pass. Committing, pushing, opening the MR/PR, and merging happen only when
the user explicitly asks ("commit and push", "raise the MR", etc.). If you
reached here without that explicit instruction, STOP and ask first.
Safe sequence
- Branch check — confirm you are NOT on
main. If you are, create a branch:git checkout -b <type>/<slug>(e.g.feat/fetch-github-repos). git statusandgit diff— confirm what will be committed.- Secret scan — one more look; abort if any key/credential is present.
- Stage intentionally — add the specific files you meant to change.
NEVER
git add -Ablindly..envmust never be staged. - Commit with a Conventional Commit message:
type(scope): imperative summary(≤72 chars, lowercase, no trailing period). Add a body explaining why only if non-obvious. - Push:
git push -u origin <branch>.
Guardrails
- One logical change per commit. Split unrelated changes.
- Only commit when tests are green (from
/test) and the diff is reviewed (from/self-review). - If this completes a ROADMAP.md item, note it —
/open-prwill check it off.
Handoff
Once pushed → hand off to /open-pr to open the pull request.
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 · 40 lines · 49 tokens per session scan A 828d1b94e69f
commit-push is a skill published in the GitHub repository justomsharma/github-resume-assistant (0 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 433 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
git-guru
Expert Git skills covering interactive rebase, worktree management, reflog recovery, bisect debugging, advanced workflows, commit message best practices, and clean history management. Use this skill when needing advanced Git operations, cleaning commit history, managing multiple worktrees, recovering lost commits…
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
git
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.