Borrowing it
Nothing to install: this file belongs to inconcept/bitbucket-mcp. 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/inconcept/bitbucket-mcp/main/.agents/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/inconcept/bitbucket-mcpWrote 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/inconcept/bitbucket-mcp/commit)<a href="https://agentmods.dev/skills/inconcept/bitbucket-mcp/commit"><img src="https://agentmods.dev/badge/skills/inconcept/bitbucket-mcp/commit/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/inconcept/bitbucket-mcp/commit"><img src="https://agentmods.dev/badge/skills/inconcept/bitbucket-mcp/commit.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.01247 |
| Opus 5.5 | $0.00014 | $0.00499 |
| Sonnet 5.5 | $0.00007 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
conventional-commit 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.
This is a copy
91% identical to conventional-commit — 81 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commit Messages
Follow these conventions when creating commits.
Prerequisites
Before committing, ensure you're working on a feature branch, not the main branch.
# Check current branch
git branch --show-current
If you're on main or master, create a new branch first:
# Create and switch to a new branch
git checkout -b <type>/<short-description>
Branch naming should follow the pattern: <type>/<short-description> where type matches the commit type (e.g., feat/add-user-auth, fix/null-pointer-error, refactor/extract-validation).
Format
<type>(<scope>): <subject>
<body>
<footer>
The header is required. Scope is optional. All lines must stay under 100 characters. NEVER use "\n" for new line.
Footer Rules
- If code in the commit was generated by an agent, include the agent as a co-author in the footer:
Co-authored-by: codex <[email protected]>Co-authored-by: claude <[email protected]>Co-authored-by: cursor <[email protected]>
- If both apply, include both footer lines.
Commit Types
| Type | Purpose |
|---|---|
build |
Build system or CI changes |
chore |
Routine maintenance tasks |
ci |
Continuous integration configuration |
deps |
Dependency updates |
docs |
Documentation changes |
feat |
New feature |
fix |
Bug fix |
perf |
Performance improvement |
refactor |
Code refactoring (no behavior change) |
revert |
Revert a previous commit |
style |
Code style and formatting |
test |
Tests added, updated or improved |
Subject Line Rules
- Use imperative, present tense: "Add feature" not "Added feature"
- Capitalize the first letter
- No period at the end
- Maximum 70 characters
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 · 181 lines · 34 tokens per session scan A dedabd45ddfc
conventional-commit is a skill published in the GitHub repository inconcept/bitbucket-mcp (4 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,247 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to conventional-commit, differing in 81 lines, and is treated as a copy.
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 8. 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 automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.