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 rexleimo/aios --skill cap-commit-pushgit clone --depth 1 https://github.com/rexleimo/aiosWrote 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/rexleimo/aios/cap-commit-push)<a href="https://agentmods.dev/skills/rexleimo/aios/cap-commit-push"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/cap-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/rexleimo/aios/cap-commit-push"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/cap-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.00029 | $0.00382 |
| Opus 5.5 | $0.00012 | $0.00153 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
cap-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 26d 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
Cap Commit Push
Overview
cap is a shorthand command that means: commit current changes and push to remote.
Trigger
- User message is exactly
cap. - Or user explicitly asks for "commit + push".
Required Workflow
- Preflight
- Run
git status --short. - If there are no changes, report no-op and stop.
- Run
- Sync Gate
- If this task changes behavior/commands/workflow, update impacted skills first.
- Keep
.codex/skills/*and.claude/skills/*in sync for shared skills.
- Stage
- Run
git add -A.
- Run
- Commit
- Prefer a Conventional Commit message based on current task context.
- Fallback message:
chore: cap snapshot <YYYY-MM-DD>.
- Push
- Run
git push. - If upstream is missing, run
git push --set-upstream origin <current-branch>.
- Run
- Report
- Return commit hash, branch, and push result.
Safety Rules
- Do not amend commits unless the user explicitly asks.
- Do not run destructive git commands (
reset --hard, forced checkout).
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.
- 26d ago Changed 5dccc59c4e5f
- 1mo ago Changed a94fdd6022cd
- 1mo ago Changed 524933f1dcc6
- 1mo ago First seen · 45 lines · 29 tokens per session scan A a9023d77c55c
cap-commit-push is a skill published in the GitHub repository rexleimo/aios (54 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 382 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
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use when committing changes, saving work, staging and committing, or choosing a conventional commit message.
post-commit
Use when a code commit just landed (not wip/amend/undo) and CHANGELOG or plugin-version post-commit actions are needed.
commit-detection
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
commit-optimization
Use when configuring settings.json to reduce commit-pro's context token usage.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (gh).
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.