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/arpitbbhayani/ape-skills/ape-commitnpx skills add arpitbbhayani/ape-skills --skill ape-commitgit clone --depth 1 https://github.com/arpitbbhayani/ape-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/arpitbbhayani/ape-skills/ape-commit)<a href="https://agentmods.dev/skills/arpitbbhayani/ape-skills/ape-commit"><img src="https://agentmods.dev/badge/skills/arpitbbhayani/ape-skills/ape-commit.svg" alt="Measured on agentmods" 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.00072 | $0.00540 |
| Opus 5 | $0.00036 | $0.00270 |
| Sonnet 5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
ape-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 5d 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.
What it actually says
Commit Message Style
Format
<short summary line>
- <change>
- <change>
- <change>
Rules
Summary line (first line)
- One line only
- Short and crisp -- aim for under 72 characters
- Use the imperative mood: "Add feature" not "Added feature" or "Adds feature"
- No trailing period
- Describe what the commit does, not how
Blank lines
- Always exactly one blank line between the summary line and the bullet list (never omit it)
- No blank lines between bullet list items -- the list must be tight and contiguous (single newline after each item, never an empty/blank line)
- No trailing blank lines at the end of the commit message
Bullet points
- Each bullet describes a single, specific change
- Short and crisp -- one line per bullet
- Keep bullet items contiguous with no blank lines between them
- Start each bullet with a verb in the imperative mood (Add, Fix, Remove, Update, Rename, Move, Extract, etc.)
- No trailing periods
- No fluff or filler words
Never include
- Blank lines between bullet list items (loose lists)
- Co-author lines (no
Co-authored-by:trailer) Generated by Claudeor any AI attribution- Redundant context already obvious from the diff
Examples
Good:
Add user authentication middleware
- Add JWT validation to protected routes
- Return 401 on missing or expired token
- Extract auth logic into separate middleware file
- Add unit tests for token validation
Fix null pointer crash on empty cart checkout
- Guard against null items array before totalling
- Add early return when cart has no items
- Log warning when checkout attempted on empty cart
Bad (do not do this):
Updated some stuff and fixed a few things that were broken and also added
some new features to the codebase
- I made some changes to the auth file because it was crashing
- Also fixed the cart thing
- Co-authored-by: Claude <[email protected]>
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.
- 5d ago First seen · 83 lines · 72 tokens per session scan A 585709e7e8e0
ape-commit is a skill published in the GitHub repository arpitbbhayani/ape-skills (32 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 540 once invoked, about $0.0004 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-30.
Other skills, from other repositories
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
commit-staged-push
Commit already-staged changes and push in one step. Use when the user asks to "commit and push staged changes", "commit and push what's staged", or "commit staged and push".
stage-commit-push
Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
quick-finalize
Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the…