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 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/commits)<a href="https://agentmods.dev/skills/monglong0214/commitlore/commits"><img src="https://agentmods.dev/badge/skills/monglong0214/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/commits"><img src="https://agentmods.dev/badge/skills/monglong0214/commitlore/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.00021 | $0.00222 |
| Opus 5.5 | $0.00008 | $0.00089 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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.
What it actually says
CommitLore commits
Use the CommitLore MCP tools for a non-trivial commit only when there is a real constraint, evaluated alternative, warning, or verification gap worth leaving for a future reader. Trivial changes commonly produce no record.
Stage the intended diff first. Call commitlore_prepare_capture, build the
draft only from the returned prompt and the actual session/diff evidence, then
call commitlore_verify_capture. If no record survives verification, commit
without one. For a surviving record, call commitlore_stage_capture immediately
before the ordinary Git commit. Do not invent quotes, hand-repair rejected
evidence, or reuse a nonce after the staged diff changes.
The repository's policy decides whether unattended capture is allowed. Never enable that policy or initialize a repository merely because this skill loaded.
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 · 25 lines · 21 tokens per session scan A 5a4a1970fed6
commitlore-commits is a skill published in the GitHub repository MongLong0214/commitlore (18 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 222 once invoked, about $0.0001 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.