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 Sistema2D/FrameCode-VibeWork --skill git-conventional-commitsgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/git-conventional-commits)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/git-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/sistema2d/framecode-vibework/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/git-conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector 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.00037 | $0.00744 |
| Opus 5.5 | $0.00015 | $0.00298 |
| Sonnet 5.5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
git-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 21d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git conventional commits
Purpose
Prepare or execute a reviewable Git commit, annotated version tag, push, or release message while preserving scope, version namespaces, and external-action authority.
Use conditions
Use when the user requests commit-message preparation, staging/commit, tag creation, push, or release-message generation. Load release-checklist as well when a version or publication is involved.
Non-responsibilities
- inferring authority to commit, tag, push, publish, merge, or rewrite history;
- staging unrelated worktree changes;
- choosing an application release record for an FCVW release, or the reverse;
- creating mandatory wiki/session records when no reusable knowledge or policy requires them;
- exposing secrets through diffs, messages, tags, or release notes.
Inputs
Valid Git worktree, status and diff, active/completed plans, application changelog or framework release record, target branch/remote, target version, validation evidence, and explicit authority for each external mutation.
Commit format
<type>(<scope>): <short imperative summary>
<optional body describing why and impact>
<optional issue, plan, or BREAKING CHANGE footer>
Common types: feat, fix, docs, refactor, test, perf, build, ci, chore, and revert. Scope names the smallest stable responsibility, not an agent or temporary filename.
A breaking footer describes the actual compatibility impact and migration, for example:
feat(schema)!: require regression contract in new plans
BREAKING CHANGE: new plans use fcvw/plan@2; plan@1 remains legacy-readable.
Procedure
- Confirm the directory is a valid Git worktree and inspect branch, remotes, status, staged diff, and unstaged diff.
- Identify user-owned pre-existing changes and exclude them unless explicitly included.
- Confirm plan, regression evidence, and application changelog or framework release record are coherent.
- Scan the intended diff for secrets, generated noise, unresolved conflicts, and out-of-scope paths.
- Select type/scope and draft a concise imperative summary; add compatibility and issue/plan references only when useful.
- Stage and commit only when authorized, then verify the resulting commit content and worktree state.
- For a version tag, confirm semantic version, namespace, release record, target commit, and publication state; create an annotated tag only when authorized.
- Push branch, tag, or release only with explicit authority and record actual remote evidence separately.
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.
- 21d ago Changed · -5 lines · +19 tokens per session 3af83be1005a
- 1mo ago First seen · 84 lines · 18 tokens per session scan A 75987208e92b
git-conventional-commits is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (29 stars, last pushed 19d ago), licensed Apache-2.0. It adds 37 tokens to every session and 744 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-30.
Other skills, from other repositories
changelog-generator
Quick Reference - Parse conventional commits and generate categorized changelog.
finish-task
Deprecated alias for close-task.
sdlc-commit
Use when committing work in a repo that follows the SDLC Enterprise Framework (SEF), or when writing a PR title and description. Stages files by name, blocks secrets, writes a conventional commit message that says why, and keeps commits small and single-purpose. It commits only; it does not push or merge.
git-automation
Advanced Git operations automation including intelligent branching, commit optimization, release workflows, and repository health management.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.