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 trebormc/drupal-ai-agents --skill commit-messagegit clone --depth 1 https://github.com/trebormc/drupal-ai-agentsWrote 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/trebormc/drupal-ai-agents/commit-message)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/commit-message"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/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/trebormc/drupal-ai-agents/commit-message"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/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.00161 | $0.02341 |
| Opus 5.5 | $0.00064 | $0.00936 |
| Sonnet 5.5 | $0.00032 | $0.00468 |
| Haiku 4.5 | $0.00016 | $0.00234 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Generate a commit message file from the current git state. The user reviews it and commits manually. This skill does NOT run git commit or git push.
Output File
The message is saved to commit-msg.txt in the project root. The user can then:
# Option A: use the file directly
git commit -F commit-msg.txt
# Option B: copy the subject line only
git commit -m "$(head -1 commit-msg.txt)"
# After committing, clean up
rm commit-msg.txt
Language Rules
- Commit messages are ALWAYS in English — Drupal community standard, same contract as the translations rule: the conversation language never leaks into the repository. A user talking in Spanish still gets an English commit message. The single exception: the user EXPLICITLY requests another language for this message.
- Technical terms (file names, function names, config keys) stay in their original form
- Never mention AI, assistants, or automated tools in the message — write as if the developer authored it
Step 1: Gather Context
Run these commands to understand the full picture:
# Overview: what files changed, how much
git diff --stat
git diff --cached --stat
# New, deleted, renamed files (not visible in diff)
git status --short
# Full diff for semantic analysis
git diff
git diff --cached
# Recent commit style for consistency
git log --oneline -10
Important distinctions:
git diff= unstaged changes (not yet added)git diff --cached= staged changes (alreadygit add-ed)- If everything is unstaged, analyze
git diff. If staged, analyzegit diff --cached. If mixed, analyze both.
Step 2: Analyze Changes
From the diff output, determine:
2a. Change Type (Conventional Commits)
| Type | When to use |
|---|---|
feat |
New functionality, new files that add capabilities |
fix |
Bug fix, error correction, broken behavior repaired |
refactor |
Code restructuring without changing behavior |
docs |
Documentation, README, comments only |
style |
Formatting, whitespace, linting fixes (no logic change) |
test |
Adding or modifying tests |
chore |
Build config, dependencies, CI, tooling |
perf |
Performance improvement |
ci |
CI/CD pipeline changes |
build |
Build system, external dependencies |
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 · 272 lines · 161 tokens per session scan A 41b78ab9ccc0
commit-message is a skill published in the GitHub repository trebormc/drupal-ai-agents (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 161 tokens to every session and 2,341 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…