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 Supersynergy/awesome-agentic-coding --skill commitgit clone --depth 1 https://github.com/Supersynergy/awesome-agentic-codingWrote 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/supersynergy/awesome-agentic-coding/commit)<a href="https://agentmods.dev/skills/supersynergy/awesome-agentic-coding/commit"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/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/supersynergy/awesome-agentic-coding/commit"><img src="https://agentmods.dev/badge/skills/supersynergy/awesome-agentic-coding/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.00019 | $0.00274 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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
Smart Commit Protocol
- Run
git statusandgit diff --cached(orgit diffif nothing staged) - Analyze ALL changes — understand the "why", not just the "what"
- Stage relevant files (never use
git add -A— be selective) - Check for accidentally included files:
.env, credentials, large binaries,node_modules - Look at recent
git log --oneline -5to match the repo's commit style - Write a concise commit message:
- First line: imperative mood, under 72 chars, focuses on WHY
- Body (if needed): bullet points of key changes
- Never include file lists — that's what
git showis for
- Commit with the message
- Show the result with
git log --oneline -1
Rules
- NEVER amend existing commits unless explicitly asked
- NEVER skip hooks (--no-verify)
- NEVER commit .env, credentials, or secrets — warn the user
- If pre-commit hook fails, fix the issue and create a NEW commit
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 · 26 lines · 19 tokens per session scan A 9228a1be9eaf
commit is a skill published in the GitHub repository Supersynergy/awesome-agentic-coding (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 274 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-31.
Other skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Generate a conventional commit message for staged changes.
git
Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
claude-devfleet
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.