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 ArdurAI/ardur-agent --skill git-commit-messagegit clone --depth 1 https://github.com/ArdurAI/ardur-agentWrote 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/ardurai/ardur-agent/git-commit-message)<a href="https://agentmods.dev/skills/ardurai/ardur-agent/git-commit-message"><img src="https://agentmods.dev/badge/skills/ardurai/ardur-agent/git-commit-message/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/ardurai/ardur-agent/git-commit-message"><img src="https://agentmods.dev/badge/skills/ardurai/ardur-agent/git-commit-message.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.00017 | $0.00178 |
| Opus 5.5 | $0.00007 | $0.00071 |
| Sonnet 5.5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
git-commit-message 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
Writing the commit message
Produce a single Conventional-Commits message describing the staged changes.
- Pick the
type:feat,fix,docs,refactor,test,chore, orperf. - Add an optional
(scope)naming the area touched. - Write an imperative, present-tense subject line of 72 characters or fewer:
type(scope): subject. - If the change needs explanation, add a blank line and a wrapped body.
For the full subject-line and body conventions this repo expects, ask for the
@./conventions.md resource (pass it in expand).
What ships with it
1 file 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 · 21 lines · 17 tokens per session scan A 0ab9c8831ae1
git-commit-message is a skill published in the GitHub repository ArdurAI/ardur-agent (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 178 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
oma-scm
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
commit-and-push
Create a well-formatted git commit and push to remote repository.
effect-ledger
Record an effect, sign an effect, reconcile an effect or check "did this PR merge" through the signed AIWG effect ledger, using one aiwg effect command with scriptable exit codes.
customize-contribute-back
Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR.
worktree
Use when the user requests a Git worktree or a development task needs an isolated directory to create, find, reuse, hand off, or clean up. Exclude read-only work, non-Git repositories, and tasks that need no separate branch or directory.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.