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 Maless88/Roadboard --skill git-conventionsgit clone --depth 1 https://github.com/Maless88/RoadboardWrote 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/maless88/roadboard/git-conventions)<a href="https://agentmods.dev/skills/maless88/roadboard/git-conventions"><img src="https://agentmods.dev/badge/skills/maless88/roadboard/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/maless88/roadboard/git-conventions"><img src="https://agentmods.dev/badge/skills/maless88/roadboard/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.00042 | $0.00315 |
| Opus 5.5 | $0.00017 | $0.00126 |
| Sonnet 5.5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
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.
What it actually says
Git conventions
Commit only when the developer (or the task prompt) explicitly asks. Never on your own initiative.
Commit format
type(scope): description — types: feat, fix, docs, style, refactor, test, chore.
Use a HEREDOC for multi-line messages so formatting stays clean.
Branches
main— stable, tagged releasesdev— default integration branchfeature/*— features ·fix/*— bugfixes
Safety rules (non-negotiable)
- Never update git config.
- Never run destructive commands (
push --force,reset --hard,checkout --,restore --,clean -f,branch -D) unless explicitly told. - Never use
--no-verifyor bypass commit signing. - Never force-push to
main/master. - Create new commits — do not amend unless explicitly asked.
- Stage specific files by name; avoid
git add -A/git add .. - Never commit secrets (
.env, credentials, anyenv/secrets.*). - Do NOT add
Co-Authored-By: Claudeor any Claude/Anthropic co-author trailer.
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 · 28 lines · 42 tokens per session scan A 09bffee706c0
git-conventions is a skill published in the GitHub repository Maless88/Roadboard (3 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 315 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-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.
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.
commit
Generate Conventional Commits spec git commits (auto-separate by feature).
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.