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 mathiasbourgoin/roster --skill git-conventionsgit clone --depth 1 https://github.com/mathiasbourgoin/rosterWrote 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/mathiasbourgoin/roster/git-conventions)<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/git-conventions"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/git-conventions/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/mathiasbourgoin/roster/git-conventions"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/git-conventions.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.00020 | $0.01091 |
| Opus 5.5 | $0.00008 | $0.00436 |
| Sonnet 5.5 | $0.00004 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
git-conventions 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Conventions
Apply standardized git conventions for the action described in $ARGUMENTS (e.g., "commit this", "create PR", "new branch for auth feature").
Steps
- Identify the action requested in
$ARGUMENTS(commit, branch, PR, or full workflow). - Apply the relevant convention sections below.
- Execute the git command(s) following the format.
Commit Format
<type>: <description>
Types: feat, fix, refactor, docs, test, chore, perf, ci
- Description: imperative mood, lowercase, no period, under 72 chars.
- Body (optional): blank line after subject, wrap at 80 chars, explain why not what.
- Footer (optional):
Closes #123,BREAKING CHANGE: <description>.
Examples:
feat: add JWT authentication middlewarefix: prevent null pointer in user lookuprefactor: extract validation into shared module
Branch Naming
<type>/<short-description>
- Kebab-case description, max 4 words.
- Examples:
feat/add-auth,fix/null-pointer,refactor/extract-validation - For issue-linked work:
feat/123-add-auth
PR Workflow
When creating a PR:
- Ensure the branch is pushed with
git push -u origin <branch>. - Write the body with the file-writing tool to
briefs/<branch-slug>-pr-body.md, then:
Template for the body:gh pr create --title "<type>: <description>" --body-file briefs/<branch-slug>-pr-body.md && rm -f briefs/<branch-slug>-pr-body.md
## Summary
- <1-3 bullet points describing what and why>
## Test plan
- [ ] <specific verification step>
- [ ] <edge case checked>
- [ ] <regression check>
- Title: same format as commit subject (
<type>: <description>), under 70 chars. - Request reviewers if the user specifies them.
Commit Workflow
When committing:
- Run
git statusandgit diff --stagedto understand what's staged. - If nothing staged, help the user stage relevant files (prefer explicit paths over
git add .). - Draft commit message following the format above.
- Write the message with the file-writing tool (not a shell command) to
briefs/<branch-slug>-commit-msg.txt—<branch-slug>is the branch name with/replaced by-, so two sessions in one checkout never overwrite each other's file — then commit from it and delete it:
Never put the message on the command line — not ingit commit -F briefs/<branch-slug>-commit-msg.txt && rm -f briefs/<branch-slug>-commit-msg.txt-m "...", not in a heredoc, not inprintf/echo: see the free-text rule below. - Run
git statusafter to confirm success.
What ships with it
1 file 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 · +11 lines 71ef3cd2e721
- 1mo ago Changed · -13 lines · +4 tokens per session 3f496a9f046b
- 2mo ago First seen · 107 lines · 16 tokens per session scan A d7bd28780d51
git-conventions is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 1,091 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-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.
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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.