Borrowing it
Nothing to install: this file belongs to pdsuwwz/chatgpt-vue3-light-mvp. 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/pdsuwwz/chatgpt-vue3-light-mvp/main/.pi/skills/conventional-commits/SKILL.mdgit clone --depth 1 https://github.com/pdsuwwz/chatgpt-vue3-light-mvpWrote 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/pdsuwwz/chatgpt-vue3-light-mvp/conventional-commits)<a href="https://agentmods.dev/skills/pdsuwwz/chatgpt-vue3-light-mvp/conventional-commits"><img src="https://agentmods.dev/badge/skills/pdsuwwz/chatgpt-vue3-light-mvp/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/pdsuwwz/chatgpt-vue3-light-mvp/conventional-commits"><img src="https://agentmods.dev/badge/skills/pdsuwwz/chatgpt-vue3-light-mvp/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.00038 | $0.00504 |
| Opus 5 | $0.00019 | $0.00252 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
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 13d 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.
What it actually says
Conventional Commits
A lightweight convention for commit messages that enables automated tooling (changelogs, releases) and improves human readability.
Format
<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]
- type: category of change (see Types below).
- scope: optional area of codebase, e.g.
auth,ui,deps. - !: indicates a breaking change (can also be in footer).
- description: short, imperative summary in present tense.
- body: detailed explanation, wrapped at ~72 chars when possible.
- footer: metadata such as
BREAKING CHANGE:or issue references.
Types
Common types used by popular tooling (commitlint, semantic-release):
- feat: new feature
- fix: bug fix
- docs: documentation only changes
- style: formatting, missing semi-colons, 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 dependencies
- ci: CI configuration and scripts
- chore: maintenance tasks
- revert: revert a previous commit
Breaking Changes
Indicate breaking changes with ! or a footer:
feat(api)!: remove deprecated endpoints
BREAKING CHANGE: `/v1/users` no longer accepts `status`.
Examples
feat(chat): add streaming response support
fix(ui): handle empty history state
refactor(store): simplify session persistence
chore(deps): bump vue to 3.5.6
Recommendations
- Keep the subject line under 72 characters.
- Use imperative mood: "add", "fix", "remove".
- Reference issues in footers:
Refs: #123orCloses #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.
- 13d ago First seen · 71 lines · 38 tokens per session scan A 84b5374d8f85
conventional-commits is a skill published in the GitHub repository pdsuwwz/chatgpt-vue3-light-mvp (574 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 504 once invoked, about $0.0002 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
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
git-master
Advanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.
oma-scm
SCM (software configuration management) and Git: branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
Use when interacting with GitHub repositories, authentication, remotes, pushes, or repository creation through the GitHub CLI and related git workflows.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.