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 randommonicle/claude-skills --skill confirm-before-pushgit clone --depth 1 https://github.com/randommonicle/claude-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/randommonicle/claude-skills/confirm-before-push)<a href="https://agentmods.dev/skills/randommonicle/claude-skills/confirm-before-push"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/confirm-before-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/randommonicle/claude-skills/confirm-before-push"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/confirm-before-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.00057 | $0.00986 |
| Opus 5 | $0.00028 | $0.00493 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
confirm-before-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 11d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confirm before push or merge
Always ask before pushing to a remote, merging to a protected branch, or fast-forwarding a protected branch. Each action needs its own explicit authorisation. Past approvals in the same session do not extend to future ones.
When this applies
This skill fires on:
- Any
git pushto a remote - Any
git mergeinto main, master, or another protected branch - Any fast-forward of a protected branch (
git push origin HEAD:main) - Any history-rewriting push (
--force,--force-with-lease) - Any merge or rebase that lands work on a protected branch
This skill applies even when the project's convention is direct-to-main solo shipping. The convention defines where work lands; this skill defines the per-action authorisation gate before it lands.
How to apply
After committing locally, summarise what's on the branch and ask before pushing. Examples:
- "Committed locally as
<sha> <message>. Three files, plus one migration. Ready to push to origin?" - "Worktree branch has two commits ahead of main. Push the branch first, then fast-forward main?"
Wait for explicit confirmation. Words like "yes", "push it", "go ahead", "proceed" are clear authorisations. Ambiguous responses ("looks good", "nice") are not.
Do not push with --force or rewrite published history without explicit per-action approval that names the force operation specifically.
Standard push order
When a multi-step push is authorised, the canonical sequence is:
- Push the local working branch to its remote tracking branch
- Verify the push landed (check
git log --oneline <remote>/<branch>) - If a protected branch fast-forward is part of the authorisation, perform it as a separate step
- Verify the protected branch tip with
git log --oneline <remote>/<protected-branch>
If any step fails, stop and report rather than continuing to the next.
What this skill does not do
Local commits do not require this gate. Commit freely; the gate is on the moment work leaves the machine or lands on a protected branch.
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.
- 11d ago First seen · 83 lines · 57 tokens per session scan A ed7dfb651883
confirm-before-push is a skill published in the GitHub repository randommonicle/claude-skills (23 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 986 once invoked, about $0.0003 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…