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 Abilityai/cornelius --skill git-commit-pushgit clone --depth 1 https://github.com/Abilityai/corneliusWrote 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/abilityai/cornelius/git-commit-push)<a href="https://agentmods.dev/skills/abilityai/cornelius/git-commit-push"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/git-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/abilityai/cornelius/git-commit-push"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/git-commit-push.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00785 |
| Opus 5.5 | $0.00008 | $0.00314 |
| Sonnet 5.5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
git-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 1mo 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit and Push
Commit and push changes to the remote repository. Shows diff for approval before committing.
Purpose
Safely commit and push all staged and unstaged changes to the remote repository. Presents changes for review before committing to prevent accidental commits.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Git status | .git/ |
X | Current repo state | |
| Working directory | ./ |
X | Modified files | |
| Remote repository | origin | X | Push destination |
Prerequisites
- Git repository initialized
- Remote origin configured
- Changes to commit (untracked or modified files)
Process
Step 1: Check Repository State
# Show current branch
git branch --show-current
# Check if there are changes to commit
git status --short
If no changes, inform user and exit.
Step 2: Review Changes (APPROVAL GATE)
Present the changes for review:
# Show summary of changes
git status
# Show detailed diff of modified files (not untracked)
git diff
# Show staged changes if any
git diff --cached
Ask user:
- Show the list of files that will be committed
- Ask for commit message (suggest based on changes)
- Confirm before proceeding
Use AskUserQuestion with options:
- "Commit all changes" (Recommended)
- "Select specific files"
- "Cancel"
Step 3: Stage and Commit
Based on user choice:
If "Commit all changes":
# Stage all changes
git add -A
# Commit with user-provided message
git commit -m "$(cat <<'EOF'
[commit message here]
Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"
If "Select specific files":
- Ask which files to stage
- Stage only those files
- Commit
Step 4: Push to Remote
# Push to current branch's upstream
git push
# If no upstream, push with -u flag
git push -u origin $(git branch --show-current)
Step 5: Verify
# Confirm push succeeded
git log --oneline -1
# Show remote status
git status
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.
- 1mo ago First seen · 151 lines · 19 tokens per session scan A ee8af40a0a45
git-commit-push is a skill published in the GitHub repository Abilityai/cornelius (110 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 785 once invoked, about $0.0001 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-30.
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.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.