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 skills/pau-vega/devkit-ai/git-conventionsnpx skills add pau-vega/Devkit-AI --skill git-conventionsgit clone --depth 1 https://github.com/pau-vega/Devkit-AIWrote 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/pau-vega/devkit-ai/git-conventions)<a href="https://agentmods.dev/skills/pau-vega/devkit-ai/git-conventions"><img src="https://agentmods.dev/badge/skills/pau-vega/devkit-ai/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.00039 | $0.00383 |
| Opus 5 | $0.00019 | $0.00192 |
| Sonnet 5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00038 |
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.
What it actually says
Git Conventions
Commit Messages
Follow conventional commits format when appropriate:
<type>: <short summary>
<optional body>
Types
| Type | Usage |
|---|---|
feat |
A new feature |
fix |
A bug fix |
refactor |
A code change that neither fixes nor adds |
chore |
Maintenance, config, deps |
docs |
Documentation only |
style |
Formatting, missing semicolons, etc. |
test |
Adding or correcting tests |
Guidelines
- Use imperative mood in the subject line ("Add feature" not "Added feature")
- Keep the subject line under 72 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the body to explain what and why, not how
Branch Naming
Use descriptive branch names with a type prefix:
<type>/<short-description>
Examples: feat/add-user-auth, fix/login-error, refactor/api-client.
PR Descriptions
Include in every PR description:
- Summary — 1-3 bullet points of what changed
- Test plan — checklist of what was verified
Secrets Protection
Never stage or commit files that contain secrets:
.envfilescredentials.json*.pemprivate keys- Any file with API keys, tokens, or passwords
Always check .gitignore before staging files.
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 · 67 lines · 39 tokens per session scan A acf23274474f
git-conventions is a skill published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 383 once invoked, about $0.0002 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 skills, from other repositories
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
clarify
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…
new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.