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 patricio0312rev/skills --skill conventional-commitsgit clone --depth 1 https://github.com/patricio0312rev/skillsWrote 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/patricio0312rev/skills/conventional-commits)<a href="https://agentmods.dev/skills/patricio0312rev/skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skills/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/patricio0312rev/skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skills/conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00053 | $0.02104 |
| Opus 5 | $0.00026 | $0.01052 |
| Sonnet 5 | $0.00011 | $0.00421 |
| Haiku 4.5 | $0.00005 | $0.00210 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- conventional-commits — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
Write standardized, semantic commit messages that enable automated versioning and changelog generation.
Core Workflow
- Analyze changes: Review staged files and modifications
- Determine type: Select appropriate commit type (feat, fix, etc.)
- Identify scope: Optional component/module affected
- Write description: Concise summary in imperative mood
- Add body: Optional detailed explanation
- Include footer: Breaking changes, issue references
Commit Message Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Commit Types
| Type | Description | Semver | Example |
|---|---|---|---|
feat |
New feature | MINOR | feat: add user authentication |
fix |
Bug fix | PATCH | fix: resolve login redirect loop |
docs |
Documentation only | - | docs: update API reference |
style |
Formatting, whitespace | - | style: fix indentation in utils |
refactor |
Code change, no feature/fix | - | refactor: extract validation logic |
perf |
Performance improvement | PATCH | perf: optimize database queries |
test |
Adding/fixing tests | - | test: add unit tests for auth |
build |
Build system, dependencies | - | build: upgrade to Node 20 |
ci |
CI/CD configuration | - | ci: add GitHub Actions workflow |
chore |
Maintenance tasks | - | chore: update .gitignore |
revert |
Revert previous commit | - | revert: undo feature flag change |
Scopes
Scopes indicate the area of the codebase affected:
# Component/module scopes
feat(auth): add OAuth2 support
fix(api): handle timeout errors
docs(readme): add installation steps
# File-based scopes
style(eslint): update linting rules
build(docker): optimize image size
# Layer scopes
refactor(service): extract user service
test(e2e): add checkout flow tests
Breaking Changes
Mark breaking changes with ! or BREAKING CHANGE footer:
# Using ! notation
feat(api)!: change response format to JSON:API
# Using footer
feat(api): change response format
BREAKING CHANGE: Response now follows JSON:API specification.
Clients must update their parsers.
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 · 319 lines · 53 tokens per session scan A 815733c1d239
conventional-commits is a skill published in the GitHub repository patricio0312rev/skills (60 stars, last pushed 8mo ago), licensed MIT. It adds 53 tokens to every session and 2,104 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
housekeep-dead-code
Apply-now dead-code removal by category — one commit each, typecheck and tests between, bisect on red, then install the Knip ratchet so it cannot grow back. Use when "delete the dead code", "remove unused files", "wire up Knip". Audit first → plan-dead-code. README/deps → workflow-housekeep.
git-commit-push
Enforces Git commit standards and conventions when committing and pushing code in Agent Mode. This rule is crucial for keeping track of changes made by agents, and should run whenever the user expresses they want to commit or push code changes made by the agent. This rule should be followed when: 1. the user wants to…
commit
Generate a conventional commit message for staged changes.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.