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 imdouglasoliveira/skills --skill conventional-commitsgit clone --depth 1 https://github.com/imdouglasoliveira/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/imdouglasoliveira/skills/conventional-commits)<a href="https://agentmods.dev/skills/imdouglasoliveira/skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/imdouglasoliveira/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/imdouglasoliveira/skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/imdouglasoliveira/skills/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.00051 | $0.02313 |
| Opus 5 | $0.00026 | $0.01156 |
| Sonnet 5 | $0.00010 | $0.00463 |
| Haiku 4.5 | $0.00005 | $0.00231 |
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 10d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured Git Workflow with Conventional Commits
Conventional Commits Standard
All commits follow Conventional Commits v1.0.0.
Commit Types
feat: New feature
fix: Bug fix
docs: Documentation changes
style: Formatting, no logic changes
refactor: Refactoring existing code
perf: Performance improvements
test: Adding or modifying tests
chore: Dependency/config updates
ci: CI/CD changes
build: Build system changes
revert: Revert previous commit
Commit Structure
<type>(<scope>): <short description>
<detailed body - optional>
<footer - optional>
Examples
# Simple
feat: add user CRUD endpoints
fix: correct email validation regex
docs: update setup instructions in README
# With scope
feat(auth): implement JWT authentication
fix(api): resolve database connection timeout
test(users): add registration test suite
# With body
feat: add reporting dashboard
Implements progress metrics dashboard with
frequency charts and performance tracking.
Closes #123
Workflow
1. Check status (git status)
2. Pull latest (git pull --rebase origin <branch>)
3. Stage changes (git add <files>)
4. Commit structured (git commit -m "type(scope): description")
5. Push (git push origin <branch>)
Rules
DO
- Follow the Conventional Commits format
- Write atomic commits (one feature = one commit)
- Use imperative mood ("add", not "added" or "adding")
- Write clear, descriptive messages
- Use scope when it adds clarity (e.g.,
feat(auth)) - Reference issues when applicable (
Closes #45)
DON'T
- Generic messages ("update", "fix", "changes", "wip")
- Multiple unrelated changes in one commit
- Empty commit messages
Detailed Steps
1. Prepare changes
# Check status
git status
# Review changes
git diff
# Stage everything (or specific files)
git add .
# or
git add file1.ts file2.ts
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.
- 10d ago First seen · 438 lines · 51 tokens per session scan A 4b7a3503bf83
conventional-commits is a skill published in the GitHub repository imdouglasoliveira/skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 2,313 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-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.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
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.