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/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/commit)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/commit"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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/random6913/claude-code-superkit/commit"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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.00016 | $0.01372 |
| Opus 5.5 | $0.00006 | $0.00549 |
| Sonnet 5.5 | $0.00003 | $0.00274 |
| Haiku 4.5 | $0.00002 | $0.00137 |
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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commit Helper
Role
Stage changes safely, draft a conventional-commit message (with optional trailers), scan the staged diff for secrets, then create one verified commit. This command commits only — it never pushes.
Hard Rules
- Stage files explicitly by path. Never run
git add -A,git add ., orgit add -u. - Never stage anything on the never-stage denylist (Step 2).
- Create the commit (Step 6) ONLY when the Step 5 secret scan found nothing, OR the user has explicitly confirmed every flagged pattern. An unconfirmed secret finding blocks the commit.
- This command creates exactly one commit. Never
git push. - Message format is
type(scope): description— imperative mood, lowercase, describing the "why". - Always end the commit body with the
Co-Authored-By: Claude <[email protected]>trailer.
Steps
1. Analyze Changes
git status
git diff --stat
git diff --cached --stat
git log --oneline -5
Done when: you know which files changed, which are already staged, and the repo's recent commit-message style.
2. Stage Files
Stage only the files that belong to this change, one path at a time: git add <path> <path> .... When the working tree mixes task files with unrelated edits, stage only the task files by explicit path and leave the rest unstaged.
Never stage:
.envfiles (secrets)credentials.json,*.key,*.pem,*.p12*.sqlite,*.db(database files)- Large binary files (images, videos, archives)
node_modules/,vendor/,__pycache__/,target/
Done when: every file intended for this commit is staged by explicit path, and re-checking git diff --cached --stat shows no denylist path staged.
3. Draft Commit Message
Analyze the diff to determine:
- Type:
feat,fix,docs,refactor,chore,test,perf,style,build,ci - Scope: component or directory name (e.g.,
backend,frontend,auth,api) - Description: concise "why" (not "what"), imperative mood, lowercase
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 · 149 lines · 16 tokens per session scan A 78c2c5a77695
commit is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 1,372 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-09-03.
Other commands, from other repositories
caveman-commit
Generate a terse caveman-style commit message for staged changes.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.