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 agentmods add commands/monglong0214/commitlore/autogit clone --depth 1 https://github.com/MongLong0214/commitloreWhat 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 | $0.00020 | $0.00210 |
| Opus 5 | $0.00010 | $0.00105 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
auto 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 yesterday.
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
!"${CLAUDE_PLUGIN_ROOT}/scripts/commitlore-run.sh" auto $ARGUMENTS
Report the output above exactly as it stands. The setting lives in
.commitlore-policy.json at the repository root and is committed with it, so
turning it on applies to everyone who clones the repository. To differ on this
machine only, auto on --local / auto off --local write
.commitlore-policy.local.json, which wins per key and is untracked by
convention — the tracked file stays as the repository wrote it. Never edit
either file yourself; the command above is their writer. The setting authorises
unattended capture but does not initiate it: this host must call
commitlore_prepare_capture with the session transcript before it runs git commit.
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.
- yesterday First seen · 18 lines · 20 tokens per session scan A 45dbf82fa158
auto is a command published in the GitHub repository MongLong0214/commitlore (9 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 210 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
deja
Search this machine's past AI coding sessions (deja-vu).
goal
Complete reference for all goal-related commands — definition, refinement, execution, review, codification, and management.
relations
Complete reference for managing relationships between entities in the knowledge graph.
decisions
Complete reference for managing architectural decision records (ADRs).
guidelines
Complete reference for managing execution guidelines — testing, coding style, process, and more.
work
Complete reference for work refine, work review, work pause, and work resume commands.