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/jgamaraalv/ts-dev-kit/conventional-commitsnpx skills add jgamaraalv/ts-dev-kit --skill conventional-commitsgit clone --depth 1 https://github.com/jgamaraalv/ts-dev-kitWrote 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/jgamaraalv/ts-dev-kit/conventional-commits)<a href="https://agentmods.dev/skills/jgamaraalv/ts-dev-kit/conventional-commits"><img src="https://agentmods.dev/badge/skills/jgamaraalv/ts-dev-kit/conventional-commits.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.1 | $0.00138 | $0.01373 |
| Opus 5 | $0.00069 | $0.00687 |
| Sonnet 5 | $0.00028 | $0.00275 |
| Haiku 4.5 | $0.00014 | $0.00137 |
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 6d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<live_context>
Staged changes (summary):
!git diff --cached --stat 2>/dev/null || echo "(nothing staged)"
Staged diff:
!git diff --cached 2>/dev/null | head -300 || echo "(nothing staged)"
Recent commits (style reference):
!git log --oneline -8 2>/dev/null || echo "(no commits yet)"
</live_context>
Table of Contents
- Format
- Types and SemVer impact
- Breaking changes
- Examples
- Non-obvious rules
- Choosing the right type
- SemVer cheatsheet
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
- type: lowercase noun (see table below)
- scope: optional noun in parentheses describing the affected section, e.g.
feat(auth): - description: imperative, present tense, no period at end, immediately after
": " - body: free-form; begins one blank line after description
- footers: one blank line after body; follow git trailer format (
Token: valueorToken #value)
Types and SemVer impact
| Type | Use for | SemVer |
|---|---|---|
feat |
New feature | MINOR |
fix |
Bug fix | PATCH |
docs |
Documentation only | none |
style |
Formatting, whitespace (no logic change) | none |
refactor |
Code restructure (not a fix or feature) | none |
perf |
Performance improvement | none |
test |
Adding or fixing tests | none |
build |
Build system, dependencies (npm, gradle…) | none |
ci |
CI configuration (GitHub Actions, CircleCI…) | none |
chore |
Maintenance not fitting above types | none |
revert |
Reverts a previous commit | none |
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.
- 6d ago First seen · 161 lines · 138 tokens per session scan A 44e2848f5c0a
conventional-commits is a skill published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 138 tokens to every session and 1,373 once invoked, about $0.0007 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-30.
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…