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/Sagargupta16/claude-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/sagargupta16/claude-skills/commit)<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/commit"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-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/sagargupta16/claude-skills/commit"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-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.00010 | $0.00302 |
| Opus 5.5 | $0.00004 | $0.00121 |
| Sonnet 5.5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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
Live state
- Status: !
git status --short - Staged stat: !
git diff --cached --stat - Staged diff: !
git diff --cached - Unstaged stat: !
git diff --stat - Recent commit style: !
git log --oneline -5
Task
Review the live state above and create a conventional commit. Do not re-fetch diffs.
Steps:
- If nothing is staged, stop and ask which files to stage. Never use
git add .orgit add -A. - Match the conventional-commit type from the staged diff:
feat,fix,refactor,docs,test,chore,style,perf,build,ci. - Match the repo's commit-style pattern shown above (prefix casing, scope usage, body length).
- Subject under 72 chars, imperative mood, no trailing period.
- If the why is not obvious from the subject, add a short body (1-3 lines).
- Never commit files that likely contain secrets (
.env,credentials.json, private keys). - Never add
Co-Authored-Bytrailers. Never push unless explicitly asked.
Output: the commit (or a refusal with reason if anything above blocks).
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 Changed 444a78fbbf4d
- 1mo ago First seen · 28 lines · 10 tokens per session scan A ae1a1b6f202b
commit is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 302 once invoked, about $0.0000 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-31.
Other commands, from other repositories
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
amend
Amend the most recent commit with additional changes or an updated message.
commit-push
Stage, commit, and push changes with an auto-generated conventional commit message.
fix-comments
Address PR review comments by implementing requested changes automatically.
ship
Prepare the current branch to ship, commit messages, semver bump, and a PR description, all for approval.
commit
Craft a single Conventional Commit message from the currently staged changes.