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 jonathan-vella/apex-accelerator --skill apex-git-commitgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/apex-git-commit)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-git-commit"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-git-commit/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/jonathan-vella/apex-accelerator/apex-git-commit"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-git-commit.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.00065 | $0.00332 |
| Opus 5.5 | $0.00026 | $0.00133 |
| Sonnet 5.5 | $0.00013 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
apex-git-commit 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 today.
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.
What it actually says
Git Commit
Prerequisites
Require the selected built-in owner agent and model MAI-Code-1.1-Flash.
This is not 01-Orchestrator or a worker.
Allowed operation tools are ask_user, execute,
read, and todo, intersected with the active owner's permissions.
A skill does not bind agent/model/tools. STOP and request manual selection
if any cannot be verified; do not widen tools or inherit a different model.
Procedure
Read apex-github-operations, then execute the shared commit procedure. Preserve exclusions, staged-index checks, normal hooks, no-main/no-force rules, failure stops, and the separate PR decision. Use git and gh only, not MCP. Do not dispatch this operation as a subagent or switch credentials implicitly.
This manual skill replaces the archived Local adapter. Runtime discovery and permissions require actual verification; source checks are not certification. Do not enable experimental skill context forks to make the operation available.
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.
- today First seen · 31 lines · 65 tokens per session scan A bf487190308d
apex-git-commit is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 332 once invoked, about $0.0003 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-10-21.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.