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-querygit 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-query)<a href="https://agentmods.dev/skills/monglong0214/commitlore/commitlore-query"><img src="https://agentmods.dev/badge/skills/monglong0214/commitlore/commitlore-query/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-query"><img src="https://agentmods.dev/badge/skills/monglong0214/commitlore/commitlore-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00143 | $0.01623 |
| Opus 5.5 | $0.00057 | $0.00649 |
| Sonnet 5.5 | $0.00029 | $0.00325 |
| Haiku 4.5 | $0.00014 | $0.00162 |
Grade A, and why
commitlore-query 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CommitLore query
context, limits, ruled-out, and warnings read the same underlying
record set for one or more paths; stale reads it repo-wide. All are
read-only — none of them touch git state.
Reading records for a path
commitlore context src/core/types.ts
context for src/core/types.ts as of 2026-07-26T07:28:42.051Z — 2 limits, 5 ruled-out, 3 warnings, 16 other in 2 records (index, 2 commit record(s) scanned)
limits
r-c0f4e2 3d249cd3 npm gitlore is held by an active same-domain CLI, so the owner's first-choice name was not available
r-b2e7f1 00d348d1 Parsing must delegate to git interpret-trailers -- reimplementing the block rules would drift from the rest of the git ecosystem
ruled-out
r-c0f4e2 3d249cd3 GitLore published as git-lore | the binary and search results still collide with the existing gitlore tool
r-b2e7f1 00d348d1 line-matching Key: prefixes | prose containing a colon line parses as a record and feeds agents false context (verified B3)
...
warnings
r-c0f4e2 3d249cd3 [directive] ADR-0008 and ADR-0009 keep the literal string Annals on purpose -- mechanical substitution there destroys the decision trail
...
other
r-c0f4e2 3d249cd3 Blast: system
...
context is every active record touching the path, grouped by section, each
line prefixed with its Record-Id and short commit sha. limits,
ruled-out, and warnings return the same underlying records filtered to
one key each — reach for those when only one kind of information matters:
commitlore limits src/core/types.ts
2 limits for src/core/types.ts as of 2026-07-26T07:28:42.946Z (index, 2 commit record(s) scanned)
r-c0f4e2 3d249cd3 npm gitlore is held by an active same-domain CLI, so the owner's first-choice name was not available
r-b2e7f1 00d348d1 Parsing must delegate to git interpret-trailers -- reimplementing the block rules would drift from the rest of the git ecosystem
Those four take zero or more paths (commitlore context a.ts b.ts answers for
both). Several paths work, but Git follows renames only for a single path.
When several paths are supplied, the CLI answers each literal path and
prints a diagnostic that renames were not followed; query one path at a time
when historical names matter.
They share these flags:
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 · 136 lines · 143 tokens per session scan A dc4c93466d78
commitlore-query is a skill published in the GitHub repository MongLong0214/commitlore (18 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,623 once invoked, about $0.0006 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
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.
crystalline-collaboration
Use when working in a domain that has a team origin on GitHub - checking status at session start, updating before deep work, sharing new knowledge as a proposal, settling a conflict, or connecting a new teammate.
github-app-bot-auth
GitHub App bot authentication — setup, token rotation, and cron refresh for jessinra-megumi-dev[bot].
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.