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/ctxr-dev/llm-wiki-memoryWrote 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/rules/ctxr-dev/llm-wiki-memory/triage-review-findings)<a href="https://agentmods.dev/rules/ctxr-dev/llm-wiki-memory/triage-review-findings"><img src="https://agentmods.dev/badge/rules/ctxr-dev/llm-wiki-memory/triage-review-findings.svg" alt="Measured on agentmods" 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.00049 | $0.00085 |
| Opus 5 | $0.00024 | $0.00043 |
| Sonnet 5 | $0.00010 | $0.00017 |
| Haiku 4.5 | $0.00005 | $0.00009 |
Grade A, and why
triage-review-findings 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 8d 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
Follow the canonical procedure (edit that file, never this shadow):
@.agents/skills/triage-review-findings.md
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.
- 8d ago First seen · 9 lines · 49 tokens per session scan A c1d69c2fd0ff
triage-review-findings is a cursor rule published in the GitHub repository ctxr-dev/llm-wiki-memory (130 stars, last pushed 11d ago), licensed MIT. It adds 49 tokens to every session and 85 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
context-loader
Use when starting a new substantive conversation or switching contexts — load relevant memories to prime the session with continuity.
memory-informed-longitudinal-work
Long-running multi-session work (research, eval loops, iterative benchmarks) — resume prior lessons, capture per-run outcomes, build up stable truths over time.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
memory-informed-design
Use when making architecture, API, or design decisions — consult prior decisions and capture new ones in-flight.
memory-informed-refactor
Use before substantive refactors — load relevant prior context, capture refactor insights as they land.
entity-detection
Pensyve entity detection — canonicalization and fallback rules for recall scoping.