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 djscheuf/agentic-dev-ecosystem-template --skill git-commitgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/git-commit)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/git-commit"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/git-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/djscheuf/agentic-dev-ecosystem-template/git-commit"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/git-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.00023 | $0.01583 |
| Opus 5.5 | $0.00009 | $0.00633 |
| Sonnet 5.5 | $0.00005 | $0.00317 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
git-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 22d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Skill
TL;DR
- First line format:
type(scope): subject(preferred) ortype(scope)for very short, self-describing changes. - First line ≤ 72 characters.
- Lowercase type and scope.
- Imperative, present-tense subject.
- Optional body and footer separated by blank lines.
- ALWAYS keep commit messages about the changes, not the tooling.
Absolute rules
No AI/tooling attribution
Commit messages describe the change, not who or what wrote it. Only the human author is accountable for commits in this repository. The message body and footer MUST NOT contain any AI/tooling attribution or provenance markers.
Forbidden content includes, but is not limited to:
Generated with [Devin](...)or any similar tool citationCo-Authored-By: Devin <...>Signed-off-by:inserted by an assistantReviewed-by:or similar trailers added by tooling- Any footer line containing a URL to an AI assistant or automation platform
Before committing, grep the drafted message for the patterns above. If any are present, delete them.
Message format
Preferred:
Short, self-describing changes use the observed repo style:
<type>(<scope>): <light details>
Use this sparingly; prefer a colon and subject for anything non-trivial.
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
Allowed types
The main branch uses these type prefixes. Prefer them in this order:
| Type | Use when |
|---|---|
feat |
A new feature or capability. |
fix |
A bug fix or correction. |
doc |
Documentation or ADR/vault changes. This repo uses doc, not docs. |
clean |
Removing, ignoring, or tidying files and configuration. |
wip |
Work-in-progress checkpoint that is intentionally committed. |
refactor |
Code restructuring without changing external behavior. |
rename |
Renaming files, skills, or symbols. |
test |
Adding or changing tests only. |
tweak |
A small adjustment to an existing feature. |
maint |
Maintenance, dependency, or tooling updates. |
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.
- 22d ago Changed · +32 lines e8b873fe88b4
- 1mo ago First seen · 156 lines · 23 tokens per session scan A d996eedfafc8
git-commit is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 1,583 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-09-13.
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.
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…
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.