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 MongLong0214/commitlore --skill commitlore-commitsgit clone --depth 1 https://github.com/MongLong0214/commitloreWrote 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/monglong0214/commitlore/commitlore-commits)<a href="https://agentmods.dev/skills/monglong0214/commitlore/commitlore-commits"><img src="https://agentmods.dev/badge/skills/monglong0214/commitlore/commitlore-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/monglong0214/commitlore/commitlore-commits"><img src="https://agentmods.dev/badge/skills/monglong0214/commitlore/commitlore-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 64 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 116 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00235 | $0.02929 |
| Opus 5.5 | $0.00094 | $0.01172 |
| Sonnet 5.5 | $0.00047 | $0.00586 |
| Haiku 4.5 | $0.00023 | $0.00293 |
Grade A, and why
commitlore-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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CommitLore commits
A CommitLore record is the trailer block at the end of a commit message —
ordinary git trailers, parsed by git interpret-trailers. It captures what the
diff itself cannot show: the conditions that shaped the decision, the
alternatives that were dropped and why, and warnings for the next agent or
person who touches this code.
Record through capture. It binds the record to a nonce, hashes the transcript and staged diff it was drafted from, and refuses any quote absent from those bytes — so a record citing something nobody said never reaches history. Hand-writing trailers skips all of that; it is the fallback at the end of this file, not the default.
When to record, and when not to
Trivial commits — typo fixes, formatting, a rename with no behavior change —
get no trailers. A record costs a future reader attention, and spending that on
noise is worse than recording nothing. Record only a real constraint, a real
alternative that was seriously considered and rejected, or a real warning worth
leaving. Answering {"records": []} is correct, and common.
Capture
This skill is the host-side initiator when the host selects it for a commit
request. The prepare-commit-msg hook that commitlore init installs only
attaches an already staged transaction; an ordinary git commit never starts
capture because it has no session transcript. Without the hook, nothing staged
reaches a commit message. Stage the change first — capture hashes git diff --cached.
1. Prepare. Write the relevant part of the session to a transcript, in the words actually exchanged rather than a summary: it is the source every quote is checked against, so paraphrasing is how a record ends up citing a sentence that was never said.
- MCP:
commitlore_prepare_capture { transcript }→{ nonce, prompt, guard_advisory, policy_error, ... } - CLI:
commitlore capture --transcript session.txtprints the same prompt.
2. Draft. That prompt is a self-contained contract — the full vocabulary,
the rule cite or omit, and the JSON to answer in: a records array, each with
trailers (key, value) and evidence (key, source of transcript or
diff, quote, locator). A quote is copied character for character; a
locator is L<start>-L<end> for transcript lines or the @@ ... @@ hunk header
for the diff. Follow the printed contract — it is the authority, and it carries
rules this file does not repeat.
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 Changed · +3 lines a3ceb089ace1
- 1mo ago First seen · 206 lines · 235 tokens per session scan A c91492e6fd48
commitlore-commits is a skill published in the GitHub repository MongLong0214/commitlore (18 stars, last pushed today), licensed MIT. It adds 235 tokens to every session and 2,929 once invoked, about $0.0009 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
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.
commit-convention
Git commit convention for Lorekeeper — enforced by commit-msg hook. Covers author identity, ticket tags, and message format for both PM (Akane) and Dev roles.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.