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 shopwareLabs/ai-coding-tools --skill commit-message-writinggit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/commit-message-writing)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/commit-message-writing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/commit-message-writing/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/shopwarelabs/ai-coding-tools/commit-message-writing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/commit-message-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00160 | $0.01310 |
| Opus 5.5 | $0.00064 | $0.00524 |
| Sonnet 5.5 | $0.00032 | $0.00262 |
| Haiku 4.5 | $0.00016 | $0.00131 |
Grade A, and why
commit-message-writing 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Generation
Generate conventional commit messages for Shopware core. Squash merge titles (title-only) for trunk merges and full commit messages (title + body) for branch work.
Output scope: Presents formatted commit message text. Does not create commits, write files, or modify git state.
Phase 1 — Detect Mode and Gather Context
Determine what we're generating — a squash merge title or a branch commit message.
- Parse user input:
- Commit ref provided (SHA, HEAD, HEAD~3, etc.) -> branch mode, resolve to SHA
- Branch ref, "squash", "current branch", or "merge commit" -> squash mode
- Nothing specific -> branch mode, use HEAD
- Gather the diff:
- Branch mode:
git show <sha> --name-status --format=''andgit show <sha> --format='' - Squash mode: Continue to step 3
- Branch mode:
- Squash mode only — detect base branch: Load
references/branch-and-pr-detection.mdand execute Steps 1-4. Route ascommit-message-writing. - Squash mode only — get branch diff:
git diff <base>...HEAD --statandgit diff <base>...HEADgit log <base>..HEAD --oneline
Phase 2 — Analyze and Generate
Type Detection
Analyze the diff to determine the commit type. Priority-ordered decision tree:
- Revert commit? ->
revert - Only docs (*.md, docblocks, inline comments)? ->
docs - Only formatting/whitespace changes? ->
style - Only test files? ->
test - Only build/dependency files (composer.json, package.json, Dockerfile)? ->
build - Only CI config (.github/workflows/, .gitlab-ci.yml)? ->
ci - Adds new user-facing functionality? ->
feat - Fixes broken behavior? ->
fix - Performance improvement (caching, query optimization, reduced allocations)? ->
perf - Code restructuring without behavior change? ->
refactor - Otherwise ->
chore
When ambiguous (e.g., both feat and fix equally present), ask the user:
AskUserQuestion(
question="This branch contains both new functionality and bug fixes. Which type best represents the primary purpose?",
options=[
{label: "feat", description: "The main goal is new functionality"},
{label: "fix", description: "The main goal is correcting broken behavior"}
]
)
What ships with it
4 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 · 131 lines · 160 tokens per session scan A fdb18d4443d5
commit-message-writing is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 3d ago), licensed MIT. It adds 160 tokens to every session and 1,310 once invoked, about $0.0006 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-30.
Other skills, from other repositories
apply
Apply a prior /repo-fleet-hygiene:audit action-plan JSON behind one fleet confirmation: default dry-run re-derives branch/worktree tips and prints the ordered batch; --apply mutates only after interactive confirmation or --yes. Owns batched merged-local-branch deletion with fail-closed OID refresh; cleans…
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and publish to npm through the release workflow. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
dev-workflow
Use when performing common development tasks like committing code, reviewing changes, running tests, fixing bugs, creating PRs, or checking repo status. Provides structured workflows for everyday git and development operations.
commit
A Git workflow for dividing uncommitted changes into meaningful commits and proposing complete commit messages before recording them.