Borrowing it
Nothing to install: this file belongs to nikicat/secrets-dispatcher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nikicat/secrets-dispatcher/master/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/nikicat/secrets-dispatcherWrote 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/nikicat/secrets-dispatcher/commit)<a href="https://agentmods.dev/skills/nikicat/secrets-dispatcher/commit"><img src="https://agentmods.dev/badge/skills/nikicat/secrets-dispatcher/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/nikicat/secrets-dispatcher/commit"><img src="https://agentmods.dev/badge/skills/nikicat/secrets-dispatcher/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.00473 |
| Opus 5.5 | $0.00006 | $0.00189 |
| Sonnet 5.5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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
Commit, Push, and Verify CI
Step 1: Pre-commit loop
Run make pre-commit and fix any failures. This target runs make check (formatting, linting, static analysis) and make test (Go tests + E2E) in parallel.
- If formatting fails: run
make fmtand re-run - If Go vet/staticcheck/tests fail: fix the code and re-run
- If frontend lint/check fails: fix the code and re-run
- Repeat until
make pre-commitexits 0
Step 2: Commit
- Run
git statusandgit diffto review all changes - Stage all relevant files (prefer explicit file names over
git add -A) - If
$ARGUMENTSis provided, use it as the commit message. Otherwise, draft a message from the changes. - Commit. Include
Co-Authored-By: Claude Opus 4.6 <[email protected]>trailer.
Step 3: Push
Push the current branch to origin:
git push
Step 4: Wait for CI
Poll GitHub checks until they complete:
gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,databaseId
- If all checks pass: done. Print the run URL and exit.
- If any check fails: proceed to step 5.
Step 5: Fix CI failures
- Fetch the failed run logs:
gh run view <run-id> --log-failed - Diagnose and fix the failure
- Run
make pre-commitlocally to verify the fix - Amend the commit:
git add <fixed-files> git commit --amend --no-edit - Force push:
git push --force-with-lease - Go back to step 4. Give up after 3 CI fix attempts and ask the user for help.
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 · 60 lines · 16 tokens per session scan A 1b3e14119a5f
commit is a skill published in the GitHub repository nikicat/secrets-dispatcher (12 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 473 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
auto-build-loop
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
gpg-signing
Configure GPG commit and tag signing, verify signatures, and plan key revocation or recovery.
git-pushing-hardened
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.