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 AuraVixStudio/caelo --skill commitgit clone --depth 1 https://github.com/AuraVixStudio/caeloWrote 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/auravixstudio/caelo/commit)<a href="https://agentmods.dev/skills/auravixstudio/caelo/commit"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/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/auravixstudio/caelo/commit"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/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.00019 | $0.00313 |
| Opus 5.5 | $0.00008 | $0.00125 |
| Sonnet 5.5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
Commit (clean, conventional) 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.
What it actually says
Commit (clean, conventional)
Use this when the user asks to commit work. Produce a focused commit with a message that explains why, not just what.
Steps
- Review. Run
git statusandgit diff(andgit diff --staged) to see exactly what changed. Read the changes — do not commit blind. - Scope. Stage only the related changes for one logical commit. If the diff mixes
unrelated work, make separate commits. Never
git add -Awithout checking what it picks up. - Message. Write a Conventional-Commits subject (
type(scope): summary, <=72 chars):feat/fix/refactor/docs/test/chore. Add a body explaining the reason and any trade-offs when the change is non-trivial. - Verify. Re-read the staged diff before committing. Do not commit secrets, debug prints, or unrelated files.
- Commit. Create the commit and report the subject line back. Push only if the user explicitly asked.
Notes
- Match the repository's existing commit style if it differs from Conventional Commits.
- One commit = one reviewable idea.
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 · 30 lines · 19 tokens per session scan A 14aa75dd68c6
Commit (clean, conventional) is a skill published in the GitHub repository AuraVixStudio/caelo (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 19 tokens to every session and 313 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
git-release-manager
Use when the user explicitly asks to prepare, tag, publish, push, or audit a Git release. Inspect branch, worktree, version metadata, changelog, tests, and release artifacts first, obtain confirmation for irreversible release actions, and record a recovery path.
pull-request-author
Use when the user asks to prepare, update, audit, or submit a pull request. Inspect repository contribution rules, branch state, diff, tests, and the target base first; create a focused reviewable change description and do not commit, push, or open a hosted pull request without explicit authorization.
commit
A checklist for preparing a Git commit summary and commit message. Git is a version-control system, and a commit records a set of code changes.
git-commit-instructions
Use when preparing git commits or PR-ready commit text; generates repository-compliant Conventional Commit messages with correct type/scope syntax, concise subject lines, and clear rationale/body formatting.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.