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 skyf0xx/hedgehog --skill conventional-commitsgit clone --depth 1 https://github.com/skyf0xx/hedgehogWrote 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/skyf0xx/hedgehog/conventional-commits)<a href="https://agentmods.dev/skills/skyf0xx/hedgehog/conventional-commits"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/conventional-commits/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/skyf0xx/hedgehog/conventional-commits"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/conventional-commits.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.00088 | $0.01399 |
| Opus 5 | $0.00044 | $0.00700 |
| Sonnet 5 | $0.00018 | $0.00280 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
conventional-commits 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 2d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
Turn uncommitted changes into a series of atomic, conventional commits
ordered for review, using Hedgehog's commit vocabulary (hedgehog-loop).
When this runs
Normally the Loop commits one step at a time as it goes — schema, then contract, then repository, and so on — so there's nothing to clean up. This skill is for when that didn't happen cleanly:
- A Correction Protocol fix touched an upstream step and several fast-forwarded dependents in one working-tree pass, needing to land as separate commits (one per step, per the Correction Protocol's own rule).
- Work happened outside the Loop's discipline (exploratory changes, a session that didn't commit as it went) and needs reconstructing into the step-shaped history Hedgehog expects.
What "atomic" means here
One commit = one build step, where that applies (one schema, one contract, one repository, etc.) — not one file. A single step may span several files (a Drizzle schema + its migration, a service + its test). If work doesn't map onto a build step (tooling, config, docs), fall back to normal atomic-commit judgment: one logical change per commit.
If a hunk can be removed without breaking the others in its commit, it belongs in its own commit.
Steps
1. Survey the working tree
Run in parallel:
git status(no-uall)git diff(unstaged)git diff --staged(anything pre-staged)git log -10 --onelineto confirm the project's existing commit style- Run
hedgehog statusfor which steps/modules are in flight
Read every changed file's diff fully before grouping — you cannot group changes you haven't read.
2. Group hunks into logical commits
For each hunk, ask: which build step is this part of, for which module?
Group by step first, module second. A hunk in the orders schema and a
hunk in the orders repository are different commits even though both
are "orders" — different steps.
Group together: a schema change with its Drizzle migration; a service with its unit test (tests land with the step they test, not a trailing "add tests" commit); config/tooling changes (lefthook, eslint boundaries, env schema) isolated from any domain step.
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.
- 2d ago Changed · -6 lines eba1aee74a71
- 12d ago First seen · 145 lines · 88 tokens per session scan A eb80945fa20a
conventional-commits is a skill published in the GitHub repository skyf0xx/hedgehog (38 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,399 once invoked, about $0.0004 per session on Opus 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
quality-gates
Graduated pre-commit quality checks that scale with project complexity and user tier. Level 0 for Builder-tier small projects, up to Level 4 for enterprise codebases. Thresholds configurable in architecture.md.
commit
Create a well-formatted conventional commit with proper message structure. Use when ready to commit changes.
using-git-worktrees
Create isolated workspaces via git worktrees for parallel development. Safety verification ensures worktree directories are gitignored before use.
finishing-a-development-branch
5-step branch completion workflow — verify tests, determine base branch, present merge options, execute, and clean up.
ticketreview-commit
Thorough code review, verify requirements met, commit with detailed message.
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.