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 softspark/ai-toolkit --skill commitgit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/commit)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/commit"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/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/softspark/ai-toolkit/commit"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00573 |
| Opus 5.5 | $0.00010 | $0.00229 |
| Sonnet 5.5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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
Git Commit
$ARGUMENTS
Creates well-structured git commits following Conventional Commits specification.
Project context
- Staged changes: !
git diff --cached --stat 2>/dev/null || echo "nothing staged" - Current branch: !
git branch --show-current 2>/dev/null
Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code restructuring |
perf |
Performance improvement |
test |
Adding/updating tests |
chore |
Maintenance tasks |
ci |
CI/CD changes |
Examples
# Feature
git commit -m "$(cat <<'EOF'
feat(search): add multi-hop reasoning support
- Implement query decomposition
- Add iterative retrieval with reasoning
- Include answer synthesis from aggregated context
EOF
)"
# Bug fix
git commit -m "$(cat <<'EOF'
fix(cache): resolve connection pool exhaustion
Root cause: connections not returned to pool on error
Solution: use context manager for automatic cleanup
Fixes #123
EOF
)"
Automated Pre-Commit Check
Run the bundled script for structured pre-commit analysis:
python3 ${CLAUDE_SKILL_DIR}/scripts/pre-commit-check.py
Use the output to validate staged changes, detect secrets, and suggest commit type/scope.
Pre-Commit Checklist
Before committing:
- Run linting:
make lint(ordocker exec {app-container} make lint) - Run tests:
make test(ordocker exec {app-container} make test) - Check for secrets: No API keys or passwords
Git Safety
- NEVER use
--forcepush without explicit request - NEVER skip hooks (
--no-verify) unless explicitly asked - ALWAYS create NEW commits (don't amend previous unless asked)
- Stage specific files, avoid
git add -Awith sensitive files
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 99 lines · 25 tokens per session scan A 6289ed68149c
commit is a skill published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed 5d ago), licensed Apache-2.0. It adds 25 tokens to every session and 573 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 skills, from other repositories
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.
git-workflow-helper
Guide pour les opérations Git complexes, résolution de conflits et bonnes pratiques de workflow. À utiliser quand l'utilisateur est bloqué avec Git ou veut mettre en place un workflow. Se déclenche aussi avec "git merge conflict", "comment revert", "git rebase", "branching strategy", "j'ai cassé mon git", ou toute…
github-readme
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.
safe-push
Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
git-workflow
Git workflow automation with conventional commits, merge vs rebase decision trees, worktrees, SSH signing, and monorepo sparse checkout patterns.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.