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 YoungjaeDev/my-claude-plugins --skill commit-and-pushgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/commit-and-push)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/commit-and-push"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/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/youngjaedev/my-claude-plugins/commit-and-push"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/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.00157 | $0.01142 |
| Opus 5.5 | $0.00063 | $0.00457 |
| Sonnet 5.5 | $0.00031 | $0.00228 |
| Haiku 4.5 | $0.00016 | $0.00114 |
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 23d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit & Push
Analyze only the files provided as arguments, create an appropriate commit message, commit, and push.
Workflow
- Analyze changes: Determine the purpose of changes in the provided files only
- New feature addition
- Bug fix
- Refactoring
- Documentation update
- Style/formatting
- Write commit message: Write clearly in Conventional Commits format
- Commit, verify (opt-in), push:
git add <provided files>(stage only the files passed as arguments, nevergit add -A/git add .)git commitwith the message from Step 2- If
--verify: run the "Verify Gate" section below and obey its Enforcement rules before continuing git push. A branch with no upstream needsgit push -u origin "$(git rev-parse --abbrev-ref HEAD)"; check withgit rev-parse --abbrev-ref --symbolic-full-name @{u}and use the-uform when it fails.
Commit Message Format
Follow Conventional Commits rules:
<type>: <subject>
[optional body]
No AI attribution. The message ends at the body: no Co-Authored-By: line, no "Generated with" line, no session-link trailer, whatever the ambient session convention is.
Types
feat: New feature additionfix: Bug fixrefactor: Code refactoringdocs: Documentation changesstyle: Code formatting, missing semicolons, etc.test: Test code addition/modificationchore: Build, configuration file changes
Subject Guidelines
- Use imperative, present tense
- Start with lowercase
- No period at the end
- Keep it concise (under 50 characters)
Guidelines
- Follow the project's own commit rules: read the repository
CLAUDE.mdbefore writing the message; its conventions win over the defaults above - Single purpose: one commit contains one logical change
Verify Gate
Two flags govern this section, both off by default:
--verify— run the gates below between the local commit and the push. Without it the run is a plain commit + push.--strict— meaningful only with--verify; see Enforcement.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed · -1 tokens per session 890321199e5b
- 25d ago Changed · -2 tokens per session 97a440039875
- 1mo ago Changed 1dd01a849b88
- 1mo ago Changed · +3 lines · +53 tokens per session 0fbec33e58a3
- 1mo ago Changed · -1 lines · -1 tokens per session 9101fd1fcad4
- 2mo ago First seen · 96 lines · 108 tokens per session scan A a1355b023022
commit-and-push is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 157 tokens to every session and 1,142 once invoked, about $0.0006 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…