Borrowing it
Nothing to install: this file belongs to ctxr-dev/llm-wiki-memory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ctxr-dev/llm-wiki-memory/main/.claude/skills/triage-review-findings/SKILL.mdgit 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/skills/ctxr-dev/llm-wiki-memory/triage-review-findings)<a href="https://agentmods.dev/skills/ctxr-dev/llm-wiki-memory/triage-review-findings"><img src="https://agentmods.dev/badge/skills/ctxr-dev/llm-wiki-memory/triage-review-findings/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/ctxr-dev/llm-wiki-memory/triage-review-findings"><img src="https://agentmods.dev/badge/skills/ctxr-dev/llm-wiki-memory/triage-review-findings.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.00055 | $0.00089 |
| Opus 5 | $0.00028 | $0.00044 |
| Sonnet 5 | $0.00011 | $0.00018 |
| Haiku 4.5 | $0.00006 | $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 12d 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.
- 12d ago First seen · 9 lines · 55 tokens per session scan A 47777ba2c459
triage-review-findings is a skill published in the GitHub repository ctxr-dev/llm-wiki-memory (131 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 89 once invoked, about $0.0003 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 skills, from other repositories
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
agentsight-code-review
A review checklist for changes in the AgentSight codebase, compared with the main branch. It checks coding rules, eBPF safety, C-language interfaces, code-size growth, and tests.
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.
latent-premises
Use when reviewing a diff or module for hidden assumptions - things the code takes for granted that nothing guarantees - or when asked "what could break this later", "what does this assume", or to harden code that works today. Complements bug-hunt: bug-hunt finds defects with triggers today; this finds the ones…
retry-safety
Use when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no…