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 agentmods add skills/youngjaedev/my-claude-plugins/commit-and-pushnpx skills add YoungjaeDev/my-claude-plugins --skill commit-and-pushgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWhat 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 | $0.00108 | $0.01086 |
| Opus 5 | $0.00054 | $0.00543 |
| Sonnet 5 | $0.00022 | $0.00217 |
| Haiku 4.5 | $0.00011 | $0.00109 |
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 2d 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 — 96 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(default OFF): run the gates in the "Verify Gate" section below. A BUILD or TEST failure aborts here — the commit stays local and nothing is pushed. A LINT failure warns only (blocks only with--strict). git push
Commit Message Format
Follow Conventional Commits rules:
<type>: <subject>
[optional body]
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
- Do not analyze files other than those provided as arguments
- Clarity: Clearly communicate what was changed and why
- Follow CLAUDE.md: Check project guidelines in
@CLAUDE.md - Single purpose: One commit should contain only one logical change
--verify(default OFF): run BUILD / TEST / LINT (+ opt-in E2E) gates between commit and push. Without the flag, behavior is unchanged — plain commit + push.--strict: only meaningful together with--verify; promotes a LINT failure from warn to a push-blocking error.
Verify Gate
Quality gates that run only when --verify is passed (Step 3.3). They run after the local commit and decide whether the push proceeds — keeping the default path (no flag) a plain commit + push.
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.
- 2d 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 7d ago), licensed MIT. It adds 108 tokens to every session and 1,086 once invoked, about $0.0005 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…