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 phuonghx/aim-cli --skill conventional-commitsgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/conventional-commits)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/conventional-commits"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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/phuonghx/aim-cli/conventional-commits"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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.00000 | $0.01113 |
| Opus 5.5 | $0.00000 | $0.00445 |
| Sonnet 5.5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00111 |
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
A structured commit history that humans skim and tools parse.
Conventional Commits 1.0 gives every commit a machine-readable prefix so changelogs and version bumps can be generated automatically.
Format
<type>[optional scope][!]: <subject>
[optional body]
[optional footer(s)]
Example:
feat(auth): add passkey login
Adds WebAuthn registration and assertion flows behind a feature flag.
Closes #142
Common types
| Type | Use for | Version impact |
|---|---|---|
feat |
A new feature | MINOR |
fix |
A bug fix | PATCH |
docs |
Docs only | — |
refactor |
Code change, no behavior change | — |
perf |
Performance improvement | PATCH |
test |
Adding / fixing tests | — |
build |
Build system or dependencies | — |
ci |
CI configuration | — |
chore |
Maintenance, no src/test change | — |
revert |
Reverts a previous commit | — |
style |
Formatting / whitespace only | — |
- Scope (optional): the area touched, e.g.
fix(parser):,feat(api):. Keep it a short noun; stay consistent across the repo.
Subject rules
- Imperative mood: "add", "fix", "remove" — not "added" / "adds" / "fixing". (It should complete: "If applied, this commit will add passkey login".)
- ≤ 72 characters, ideally ≤ 50.
- No trailing period. Lowercase first word (unless a proper noun).
- Describe what/why, not how. Put detail in the body, wrapped at ~72 cols.
Breaking changes
Two equivalent signals — use one or both:
feat(api)!: drop support for v1 tokens
and/or a footer (always uppercase, in the footer block):
BREAKING CHANGE: v1 tokens are rejected; clients must migrate to v2.
A breaking change triggers a MAJOR bump regardless of type.
Footers
BREAKING CHANGE: <description>- Issue refs:
Closes #123,Refs #98 Co-Authored-By: Name <email>
Pre-commit sanity checklist
Run through this before every commit:
- No leftover debug: no stray
console.log,print,debugger,dd(), commented-out blocks. - No unresolved markers: no
TODO/FIXME/XXXyou intended to finish in this change. - No secrets: no keys, tokens, passwords,
.envvalues, or private URLs in the diff. - Tests pass and lint/format/type checks are green.
- Diff is focused: one logical change per commit; unrelated edits split out.
- Type & scope are accurate; subject is imperative and ≤ 72 chars.
- Breaking change flagged with
!and/orBREAKING CHANGE:if behavior or API changed incompatibly.
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 · 118 lines · 0 tokens per session scan A 80edd89dc95e
conventional-commits is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,113 tokens. 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
git-flow
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
eg-precommit-review
Run a Codex-native pre-commit independent-review loop on pending changes.
fix-pr-commit-titles
Bulk-rewrite commit titles on a PR branch to match [LKPR-N] format using filter-branch — avoids per-commit hook re-runs.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
proposal-filing
File a new Lorekeeper proposal ticket — create markdown, create GitHub issue, commit, push. Use when requesting a new feature, filing a bug, or submitting a product idea.