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 pantheon-org/tekhne --skill conventional-commitsgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/conventional-commits)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/conventional-commits"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/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/pantheon-org/tekhne/conventional-commits"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/conventional-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 152 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 169 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00106 | $0.02298 |
| Opus 5 | $0.00053 | $0.01149 |
| Sonnet 5 | $0.00021 | $0.00460 |
| Haiku 4.5 | $0.00011 | $0.00230 |
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 8d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mindset
Conventional Commits exist to make commit history machine-readable. The type prefix is a contract: feat triggers a MINOR version bump, fix triggers PATCH, and ! or BREAKING CHANGE: triggers MAJOR. Every commit is a semantic event, not just a description of code changes.
Write the header for the person reviewing a CHANGELOG six months from now, not for yourself today. The body explains why — the code already shows what.
A less obvious implication: scope consistency drives changelog quality more than type correctness. A perfectly typed feat with an ad-hoc scope like feat(getUserById): produces a one-line changelog group with no neighbours. Establish a fixed scope vocabulary early — see Scope Naming and Commit Strategy.
When to Use
Apply when the user asks for help writing commit messages, wants to format staged changes as a commit, needs a CHANGELOG entry, or mentions conventional commits, semantic versioning, or version bumps.
When not to use: skip this skill if the project explicitly avoids Conventional Commits (e.g. uses Angular-style without the spec, or enforces a custom pattern via a project-specific hook). Do not override confirmed project conventions.
Procedure
- Inspect the change — read the diff or the user's description. Identify whether it adds new behaviour, fixes existing behaviour, or neither.
- Choose the type — use the Type Reference table. Decision rules for common ambiguities:
refactorvsfeat: does the user gain new capability? If yes →featfixvsrefactor: does the change correct wrong behaviour? If yes →fixperfvsrefactor: is there a measurable latency/throughput improvement? If yes →perfchorevs anything else: if another type fits, use it —choreis the last resort- Multiple types needed? Split into multiple commits (see Atomic Commits)
- Pick the scope — use the module, package, or layer name (e.g.
auth,checkout,api). Omit scope when the change is truly cross-cutting. Use a fixed vocabulary if the project defines one. See scope naming for conventions. - Draft the header — imperative mood, lowercase, ≤ 72 characters. Verify with: "If applied, this commit will
<header>." - Add a body if needed — only when the why is not obvious. Explain the reasoning, not the implementation. Wrap at 72 characters.
- Add footers —
Closes: #Nfor issue references;BREAKING CHANGE: <description>whenever the public API surface changes. Always pair!with aBREAKING CHANGE:footer. - Verify before committing — run
git commit --dry-runor your local commitlint hook to catch formatting violations before they enter history.
What ships with it
22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .audits/2026-02-21/analysis.md 8.1 KB
- .audits/2026-02-21/audit.json 145 B
- .audits/2026-02-21/remediation-plan.md 236 B
- .audits/2026-02-22/analysis.md 8.1 KB
- .audits/2026-02-22/audit.json 145 B
- .audits/2026-02-22/remediation-plan.md 236 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 417 B
- .audits/2026-03-02/remediation-plan.md 2.4 KB
- .audits/2026-04-08/analysis.md 1.2 KB
- .audits/2026-04-08/audit.json 495 B
- .audits/2026-04-08/remediation-plan.md 2.1 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 250 B
- CHANGELOG.md 736 B
- evals/scenario-01.md 3.8 KB
- evals/scenario-02.md 3.4 KB
- evals/scenario-03.md 3.2 KB
- evals/scenario-04.md 3.8 KB
- evals/scenario-05.md 4.1 KB
- references/scope-and-strategy.md 2.1 KB
- references/tooling.md 1.1 KB
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.
- 8d ago First seen · 188 lines · 106 tokens per session scan A f1a6d0df1ac8
conventional-commits is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 2,298 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
agent-commit
Analyze changes and create a meaningful commit with agent authorship. Internal skill for evolveloop.