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 joris887/exosuit --skill commitgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/commit)<a href="https://agentmods.dev/skills/joris887/exosuit/commit"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/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/joris887/exosuit/commit"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/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.00021 | $0.00348 |
| Opus 5.5 | $0.00008 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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
Create a conventional commit for staged changes.
1. Review Changes
git status
git diff --staged
2. Determine Commit Type
Based on changes, select appropriate type:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, no code change
- refactor: Code restructuring
- perf: Performance improvement
- test: Adding/updating tests
- build: Build system or dependency changes
- ci: CI configuration changes
- chore: Maintenance tasks
3. Generate Commit Message
Format:
<type>(<scope>): <short description>
<detailed body if needed>
Co-Authored-By: Claude <[email protected]>
Arguments provided: $ARGUMENTS
4. Execute Commit
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<body>
Co-Authored-By: Claude <[email protected]>
EOF
)"
5. Verify
git log -1 --oneline
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 · 73 lines · 21 tokens per session scan A 4553e11bf424
commit is a skill published in the GitHub repository joris887/exosuit (8 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 348 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.
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
pr-writing
Use whenever writing a PR title/description, a commit message body, a code review comment, or an issue — in Hedgehog's own repo or any consuming project. Triggers on "open a PR", "write the PR description", "comment on this PR", "file an issue". Covers writing style (terse, info-dense, Simplified Technical English)…
hedgehog-orchestrating
Use at the start of any session on a project with a build graph (.hedgehog/hedgehog.db), and again at every claim/dispatch/verify cycle within it. Owns consuming the build graph — claiming task packets, delegating each to the layer's agent, running hedgehog verify to gate the commit, recording debt and decisions, the…
intuitive-squash
Safely rewrite noisy local history into reviewable commits, with aggressive or moderate plan choices, when the user explicitly asks to squash.