Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/conventional-commits/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/conventional-commits)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/conventional-commits"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/conventional-commits/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/sponge-b0b/polaris/conventional-commits"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/conventional-commits.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.00047 | $0.00773 |
| Opus 5 | $0.00023 | $0.00387 |
| Sonnet 5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
conventional-commits 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Guidelines
Objective
Structure every Git commit message in strict compliance with the Conventional Commits 1.0.0 specification. Never write generic, conversational, or vague commit summaries (e.g., do not use "wip", "updated files", or "fixed bug").
Message Structure Blueprint
Every commit message must follow this structural schema exactly:
<type>[scope]: <description>
[optional body describing why the change was made]
- Type: Must be entirely lowercase. Use only the approved structural types listed below.
- Scope: Required. Represents the specific software layer or folder module modified, wrapped in lowercase parentheses (e.g.,
(reranker),(api),(db)). - Description: Written in the imperative mood (e.g., use
addinstead ofadded,fixinstead offixes). Do not capitalize the first letter and do not add a trailing period.
Approved Structural Types
Map code changes strictly to these categories:
feat(scope): Used when introducing a brand-new application feature or operational capability to the codebase.fix(scope): Used when correcting an active bug, permission block, error log, or software crash.docs(scope): Used for changes restricted entirely to documentation layout text, markdown headers, and user guides.chore(scope): Used for routine maintenance operations: package/dependency management, editing configurations (.gitignore,pyproject.toml,.graphifyignore), or adding static asset/image files.refactor(scope): Used for optimization or structural alterations to production code that do not change its runtime features or behavior.test(scope): Used when generating unit tests, increasing coverage matrix setups, or altering testing suites.ci(scope): Used for orchestration scripts, automated pipelines, deployment assets, or Docker Compose structures.
Handling Breaking Changes
If an engineering operation changes the system's foundational layout or breaks backward compatibility, append an exclamation point (!) directly to the commit type prefix and write BREAKING CHANGE: in the commit message body explaining the required manual migration layout steps.
Example: feat(db)!: switch token storage mapping to postgresql
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.
- 9d ago First seen · 60 lines · 47 tokens per session scan A 0db5875d42bf
conventional-commits is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 773 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…