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.
git clone --depth 1 https://github.com/docwilde/LOREWrote 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/commands/docwilde/lore/pending)<a href="https://agentmods.dev/commands/docwilde/lore/pending"><img src="https://agentmods.dev/badge/commands/docwilde/lore/pending/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/commands/docwilde/lore/pending"><img src="https://agentmods.dev/badge/commands/docwilde/lore/pending.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.00011 | $0.00517 |
| Opus 5.5 | $0.00004 | $0.00207 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
pending 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 19d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 19d ago Changed efd842576064
- 21d ago Changed 4fb8c7e3165c
- 1mo ago Changed 5a377bc8bc77
- 1mo ago First seen · 7 lines · 11 tokens per session scan A f49b433925d4
pending is a command published in the GitHub repository docwilde/LORE (2 stars, last pushed 5d ago), licensed AGPL-3.0. It adds 11 tokens to every session and 517 once invoked, about $0.0000 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 commands, from other repositories
pm-crystallize
Promote a project-local lesson to /.great-pm/decisions.md (cross-project memory) when it has 3+ hits with high confidence. Surfaces candidates as PROPOSALS — never auto-promotes; human approval required.
rlm-load
Load a file into an RLM buffer with chunking.
memory-init
Initialize local memory store + vector index for this project.
query
Query the wiki under one of three postures — research, contradictor, synthesis. Trigger FR — interroger le wiki, consulter le wiki, rechercher dans le wiki, contredire une thèse, synthétiser ce qu'on sait.
recall-maintain
Run maintenance on the memory system. Primary function: pressure-based demotion when working memory exceeds the word budget. Secondary: stale entry verification, contradiction checks, open loop review.
recall-init-ids
Add ^tr IDs to untagged memory entries in managed files. This is safe to run multiple times - it only tags entries that don't already have IDs.