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 bestdeejay-design/agent-skills --skill commit-message-writergit clone --depth 1 https://github.com/bestdeejay-design/agent-skillsWrote 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/bestdeejay-design/agent-skills/commit-message-writer)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/commit-message-writer"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/commit-message-writer/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/bestdeejay-design/agent-skills/commit-message-writer"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/commit-message-writer.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.00110 | $0.01373 |
| Opus 5.5 | $0.00044 | $0.00549 |
| Sonnet 5.5 | $0.00022 | $0.00275 |
| Haiku 4.5 | $0.00011 | $0.00137 |
Grade A, and why
commit-message-writer 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Writer
Conventional Commits из вашего staged-diff за один шаг.
Загружай этот скилл когда нужно написать сообщение коммита по уже
застейдженным изменениям (git add уже сделан). Скилл анализирует diff,
определяет тип и scope, выдаёт готовое сообщение в формате
Conventional Commits.
When to use
Use this skill when:
- Изменения уже застейджены (
git add), нужно сообщение коммита - Нужно привести формат к Conventional Commits (CI требует
commitlint) - Нужно автоматически определить scope по путям файлов
- Нужен короткий заголовок + тезисный body (если diff большой)
Do NOT use when:
- Изменения ещё не застейджены — сначала
git addилиgit add -p - Требуется разбить изменения на несколько логических коммитов — сначала разбей, потом вызывай скилл для каждой части
- Это squash/rebase/merge коммит — скажи об этом явно
What this skill does
Inputs
staged(default): анализируетgit diff --cached(только staged)--unstaged(опция): аналогично для unstaged (не рекомендуется)--scope(опция): принудительный scope вместо автодетекта--emoji(опция): добавить gitmoji-префикс перед типом (✨ feat: ...)
Outputs
- Готовое сообщение коммита (1 строка заголовок + опциональный body),
копируемое командой
git commitили в файлCOMMIT_EDITMSG. - Краткая справка: тип, scope, почему выбран именно этот тип.
How to use
Шаг 1: убедись, что изменения застейджены
git add <file1> <file2>
git diff --cached --stat # проверить, что видит скилл
Шаг 2: сгенерировать сообщение
python3 scripts/suggest.py --cached
Пример вывода:
✨ feat(api): add GET /v1/health endpoint with liveness probe
- expose /v1/health via Fastify (src/routes/health.ts)
- add HealthService with process uptime + memory gauge
- wire route into router bootstrap (src/app.ts)
Type: feat — new endpoint, backwards-compatible addition
Scope: api — paths match src/api/** or src/routes/**
What ships with it
2 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 Changed · +9 lines 7c60b44672e9
- 1mo ago First seen · 137 lines · 110 tokens per session scan A a5c94f65ed51
commit-message-writer is a skill published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,373 once invoked, about $0.0004 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
orca-cli
Use the public orca CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree"…
safety
Check secret handling, staged changes and push targets, destructive Git operations, Docker image hygiene, and new dependencies before consequential coding actions. Use for commits, pushes, container builds or publishes, dependency additions, and explicit safety reviews.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
setup-pre-commit
A setup for Husky pre-commit checks in a JavaScript or TypeScript repository. A pre-commit hook runs automatically before a Git commit and can format staged files, check types, and run tests.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…