Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jessinra/Lorekeepernpx agentmods add skills/jessinra/lorekeeper/commit-conventionWrote 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/jessinra/lorekeeper/commit-convention)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/commit-convention"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/commit-convention/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/jessinra/lorekeeper/commit-convention"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/commit-convention.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.00038 | $0.00640 |
| Opus 5.5 | $0.00015 | $0.00256 |
| Sonnet 5.5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
commit-convention 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Convention
All commits to the Lorekeeper repo are enforced by .git/hooks/commit-msg (installed via scripts/lorekeeper-setup.sh).
Author Identity
| Role | user.name |
user.email |
|---|---|---|
| PM (Akane) | Akane (PM) |
[email protected] |
| Dev | Dev |
[email protected] |
| Engineer (Diana) | Diana |
[email protected] |
Set locally in the repo (not globally, to avoid polluting other projects):
# PM
git config --local user.name "Akane (PM)"
git config --local user.email "[email protected]"
# Dev
git config --local user.name "Dev"
git config --local user.email "[email protected]"
# Diana
git config --local user.name "Diana"
git config --local user.email "[email protected]"
Commit Title Format
[LKPR-N] type: short imperative title
Ticket Tags
| Tag | When to use |
|---|---|
[LKPR-N] |
Work tied to a specific ticket (feature, fix, refactor, test) |
[LKPR-0] |
Housekeeping with no ticket — chore, backlog edits, moving tickets, changing status, updating skills, docs-only |
Types
feat, fix, docs, refactor, test, chore, perf
Examples
[LKPR-6] feat: add iterative search with relevance cutoff
[LKPR-19] fix: enable FK constraints via PRAGMA foreign_keys=ON
[LKPR-0] chore: add LKPR-21 entity-resolution backlog ticket
[LKPR-0] docs: update README scoring formula
[LKPR-0] chore: move LKPR-15 to done/
Merge Commits
Merge commits (branch → main) are exempt from the hook — detected by the presence of MERGE_HEAD or a title starting with Merge branch.
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 · 93 lines · 38 tokens per session scan A bd041eee7030
commit-convention is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 640 once invoked, about $0.0002 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-31.
Other skills, from other repositories
commitlore-commits
Use when about to make a git commit and there is decision context worth recording — a constraint that shaped the change, an alternative that was tried and dropped, a warning for whoever touches this next. Drives the CommitLore capture pipeline, which drafts a record from the session transcript and the staged diff…
commitlore-setup
Use when a git repository needs CommitLore wired up for the first time, or when its hook/notes configuration looks broken. Runs the diagnostic, installs the commit-msg validation hook, fixes the notes fetch refspec so records survive a clone or fetch, and builds the local record index. Trigger phrases include "set up…
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.
commitlore-commits
Capture a decision record from verified session and diff evidence before a commit.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
conventional-commits
Writes commit messages that follow the Conventional Commits 1.0 spec — type(scope): subject with an imperative subject, optional body, and breaking-change markers (! and BREAKING CHANGE:). Use when committing changes, reviewing a commit message, or wiring automated changelogs and semantic versioning. Backs AIM's…