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 agentmods add commands/mathiasbourgoin/roster/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/commands/mathiasbourgoin/roster/git-conventions)<a href="https://agentmods.dev/commands/mathiasbourgoin/roster/git-conventions"><img src="https://agentmods.dev/badge/commands/mathiasbourgoin/roster/git-conventions.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00793 |
| Opus 5 | $0.00008 | $0.00396 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
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 4d 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 — 107 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>. - Use
gh pr createwith this template:
## 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.
- Use a HEREDOC for the message:
git commit -m "$(cat <<'EOF' <type>: <description> EOF )" - Run
git statusafter to confirm success.
Rules
- Never force-push to
mainormaster. - Always push with
-uto set upstream tracking. - Never use
git add .orgit add -A— stage specific files. - Never skip pre-commit hooks (
--no-verify). - Never commit
.env, credentials, or secrets — warn the user if these are staged. - PR descriptions must be comprehensive — reviewers should understand the change without reading code.
- One logical change per commit. Split unrelated changes into separate commits.
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.
- 4d ago First seen · 107 lines · 16 tokens per session scan A d7bd28780d51
git-conventions is a command published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 8d ago), licensed MIT. It adds 16 tokens to every session and 793 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.