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 filipebraida/adonisjs-starter-kit --skill git-commitgit clone --depth 1 https://github.com/filipebraida/adonisjs-starter-kitWrote 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/filipebraida/adonisjs-starter-kit/git-commit)<a href="https://agentmods.dev/skills/filipebraida/adonisjs-starter-kit/git-commit"><img src="https://agentmods.dev/badge/skills/filipebraida/adonisjs-starter-kit/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/filipebraida/adonisjs-starter-kit/git-commit"><img src="https://agentmods.dev/badge/skills/filipebraida/adonisjs-starter-kit/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01271 |
| Opus 5.5 | $0.00019 | $0.00508 |
| Sonnet 5.5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
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 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Create semantic git commits that match the existing history in this repo. Analyze the actual diff to pick the right type, an optional scope, and a subject that reads well next to git log --oneline. Body explains the why — the diff already shows the what.
Commit format
<type>(<optional-scope>): <imperative subject>
[optional body — WHY, not WHAT]
[optional footer(s)]
- Subject: imperative mood, English, ≤ 70 characters. No trailing period.
- Scope: the single module or package most affected. Omit when the change is cross-cutting.
- Body: explain motivation (constraint, incident, decision). The diff already shows what.
- Footers:
Closes #123,BREAKING CHANGE: …, etc.
Commit types
| Type | When |
|---|---|
feat |
New user-visible capability |
fix |
Bug fix (behavior was wrong, now correct) |
refactor |
Internal change, same behavior |
test |
Add or adjust tests |
db |
Schema / migration change |
ci |
Pipeline, actions, coverage, release plumbing |
chore |
Housekeeping (deps, config, tooling) that isn't ci or db |
docs |
Docs-only change |
style |
Formatting only (no logic) |
perf |
Change motivated by a measurable performance win |
Scopes
Only use a scope when the change clearly centers on one area. Common shapes:
- Domain module: name of the module the diff sits in (
auth,users,<feature>). - Monorepo package: name of the package (
ui,eslint-config,typescript-config,skills). - Cross-cutting infrastructure (docker, CI, tooling at the repo root): usually no scope.
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 · 148 lines · 47 tokens per session scan A b478115530d3
git-commit is a skill published in the GitHub repository filipebraida/adonisjs-starter-kit (96 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,271 once invoked, about $0.0002 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
docs
Documentation drift detection and sync via oma-docs. Verify mode finds broken refs in docs//.md, sync mode proposes patches for docs affected by a git diff.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
commit
Generate Conventional Commits spec git commits (auto-separate by feature).
tuturuuu-commit
Create scoped Tuturuuu commits and perform user-authorized pushes.
commit
Use when committing changes to git - provides best practices for staging, commit messages, signing, and handling hook failures.
git-commits
Write clear, semantic git commit messages and PR/MR titles following Conventional Commits. Use when the user asks to write commit messages, format git history, improve commit quality, or set a PR/MR title, or mentions "commit message", "conventional commits", "merge message", or "git history". For the full PR/MR body…