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 tuliosousapro/SaaS-blueprint --skill conventional-commitsgit clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprintWrote 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/tuliosousapro/saas-blueprint/conventional-commits)<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/conventional-commits"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/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/tuliosousapro/saas-blueprint/conventional-commits"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/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.00034 | $0.00605 |
| Opus 5.5 | $0.00014 | $0.00242 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits Skill
When to Use
- Every time a git commit is made
- When the user asks to "commit this" or "save progress"
- When auto-committing after task completion
Reference
Instructions
1. Commit Message Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
2. Types
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
docs |
Documentation only changes |
style |
Formatting, missing semicolons, etc. (no code change) |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
Performance improvement |
test |
Adding or correcting tests |
build |
Build system or external dependency changes |
ci |
CI configuration changes |
chore |
Other changes that don't modify src or test files |
3. Scope (Optional)
Use the BRAINIAC phase or module name:
feat(idea): add competitor analysis playbookdocs(planning): update tech stack playbookfeat(skills): add market-research skillfix(landing-page): correct CTA link
4. Breaking Changes
Add ! after type/scope for breaking changes:
feat(api)!: change authentication flow to OAuth2
Or use footer:
feat(api): change authentication flow
BREAKING CHANGE: JWT tokens are no longer accepted.
5. Examples
feat(idea): add structured competitor analysis playbook
docs(skills): create market-research skill with Firecrawl integration
fix(landing-page): correct hero section gradient on mobile
chore(tasks): reset todo.md for foundations sprint
refactor(playbooks): rewrite idea phase to match new template
6. Rules
- Description: lowercase, imperative mood, no period at end
- Max 72 characters for the first line
- Body wraps at 100 characters
- One logical change per commit
- Reference issue numbers in footer when applicable:
Refs: #123
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 · 90 lines · 34 tokens per session scan A 072710f7863b
conventional-commits is a skill published in the GitHub repository tuliosousapro/SaaS-blueprint (5 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 605 once invoked, about $0.0001 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
commit-convention
Professional Commit Convention Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
commit
Creates a well-formed git commit following conventional commit format with type, scope, and descriptive message. Use when the user is ready to commit changes or mentions conventional commits.