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 Kevin-Liu-01/Agent-Machines --skill commit-and-pushgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/commit-and-push)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/commit-and-push"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/commit-and-push.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.00808 |
| Opus 5 | $0.00036 | $0.00404 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and Push
Handle the common "just get this committed and pushed" workflow without drifting into PR creation.
When to use
Use this skill when the user explicitly wants git changes committed and pushed, but does not ask for a pull request.
Examples:
- "commit and push"
- "commit these to a new branch called
kevin/updated-dashboard" - "stage this and push it"
- "push the current work with an explanation of the changes"
If the user wants a PR too, use yeet instead.
Workflow
1. Inspect before staging
Always gather context first:
git status --short
git diff --stat
git diff --cached --stat
git log --oneline -6
You are looking for:
- unrelated dirty files
- generated artifacts
- screenshots, traces, or browser logs
- obvious secrets (
.env, credentials, tokens) - the repo's recent commit style
2. Decide branch behavior
- If the user provided a branch name, use it.
- If the current branch is already a feature branch, stay on it unless the user asked otherwise.
- If the current branch is
main/masterand the user did not explicitly ask to push there, create a feature branch first, preferablykevin/<slug>.
Use non-destructive branch commands only:
git switch -c <branch>
git switch <branch>
Never use git checkout or git restore as the default path.
3. Stage intentionally
Do not blindly add everything if the tree includes junk. Exclude generated browser artifacts, scratch outputs, and anything that should not ship.
Typical exclusions:
.playwright-mcp/- screenshots or trace dumps created only for verification
- local env files
- transient build output unless the repo intentionally tracks it
If the user said "everything," interpret that as everything relevant to the requested work, not every piece of machine exhaust in the working tree.
4. Validate once if warranted
If the changes are code and the repo has an obvious targeted validation command, run it once before committing. Prefer the narrowest meaningful check.
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 First seen · 126 lines · 71 tokens per session scan A 7f86df2d06ce
commit-and-push is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (26 stars, last pushed 7d ago), licensed MIT. It adds 71 tokens to every session and 808 once invoked, about $0.0004 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-30.
Other skills, from other repositories
secrets-leak-scan
Use when sweeping for hardcoded secrets, accidentally-committed credentials, or .env leaks across the working tree and git history.
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…
commit
Read this skill before making git commits.
git-workflow
Git workflow and conventions. Use when a Dev or DSO needs to commit, branch, or open a pull request following the team standard.
pr-reviewer
Review a pull request and process review comments left by others.
commitlore-commits
Use when about to make a git commit and there is decision context worth recording — a constraint that shaped the change, an alternative that was tried and dropped, a warning for whoever touches this next. Drives the CommitLore capture pipeline, which drafts a record from the session transcript and the staged diff…