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.
git clone --depth 1 https://github.com/rana/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/commands/rana/skills/commit)<a href="https://agentmods.dev/commands/rana/skills/commit"><img src="https://agentmods.dev/badge/commands/rana/skills/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/commands/rana/skills/commit"><img src="https://agentmods.dev/badge/commands/rana/skills/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.00000 | $0.00423 |
| Opus 5.5 | $0.00000 | $0.00169 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 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
Draft a commit message from the current changes, then stage, commit, and sync with the remote.
Steps
- Run
git status(never use-uall) to see untracked and modified files. If there are no changes, inform the user and stop. - Run
git diffto see unstaged changes, andgit diff --cachedto see staged changes. - Run
git log --oneline -10to see recent commit message style. - Do NOT commit files that likely contain secrets (
.env,credentials.json, etc.). Warn the user if any are present. - Analyze all changes and draft a concise commit message:
- Summarize the nature of the changes (new feature, enhancement, bug fix, refactor, docs, test, etc.).
- Use the imperative mood (e.g., "Add", "Fix", "Update", "Remove").
- Keep the subject line under 72 characters.
- Add a body with bullet points if the changes span multiple concerns.
- Match the style and conventions visible in recent commits.
- Stage all relevant changed files by name (prefer explicit file names over
git add -A). Usegit add -Aonly if the number of changed files makes individual staging impractical (more than ~15 files). - Commit using a HEREDOC for the message to preserve formatting:
git commit -m "$(cat <<'EOF' <message> Co-Authored-By: Claude Opus 4.6 <[email protected]> EOF )" - If the commit fails due to a pre-commit hook, fix the issue, re-stage, and create a NEW commit (never amend).
- Run
git pushto sync with the remote. If the current branch has no upstream, usegit push -u origin <branch>. - Run
git statusto confirm clean working tree and show the result to the user.
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 · 28 lines · 0 tokens per session scan A d17a5ecb6480
commit is a command published in the GitHub repository rana/skills (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 423 tokens. 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-31.
Other commands, from other repositories
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
worktree
Manage git worktrees for isolated feature development.
ia-changelog
Create engaging changelogs for recent merges to main branch.