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 felipesauer/mnema --skill review-checklistgit clone --depth 1 https://github.com/felipesauer/mnemaWrote 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/felipesauer/mnema/review-checklist)<a href="https://agentmods.dev/skills/felipesauer/mnema/review-checklist"><img src="https://agentmods.dev/badge/skills/felipesauer/mnema/review-checklist/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/felipesauer/mnema/review-checklist"><img src="https://agentmods.dev/badge/skills/felipesauer/mnema/review-checklist.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.00035 | $0.00286 |
| Opus 5.5 | $0.00014 | $0.00114 |
| Sonnet 5.5 | $0.00007 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
review-checklist 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 6d 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
Review checklist
One pass. Work through these in order and write down what you did not do.
- The claim. What does the change say it does? Find the sentence in the description or the commit. Everything below is checked against it.
- The diff against the claim. Does each hunk serve the claim? Name any hunk that does not.
- The callers. For each changed function or rule, find who uses it. A change that is right for the caller you saw can be wrong for the one you did not.
- The tests. Does a test fail if the behaviour breaks? Prefer one that asserts a value over one that only runs the code.
- The edges. Empty input, the largest input, a second call, a failure halfway.
- The words. Do the messages, comments and documentation say only what the code does?
The verdict
State it first: approve, approve with remarks, or do not approve. Separate what blocks from what is a remark. Close with the list of what you did not check.
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.
- 6d ago First seen · 25 lines · 35 tokens per session scan A 252cca9810a6
review-checklist is a skill published in the GitHub repository felipesauer/mnema (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 286 once invoked, about $0.0001 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-10-10.
Other skills, from other repositories
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
code-review
Review a diff against its acceptance criteria in four segments (convention adherence, bug scan, historical-context regressions, test-coverage gaps) as a NON-implementing agent. Findings are sorted by severity, each with file:line + a failure scenario. A planted defect must be caught; a clean diff must not be…
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
eval-leakage-audit
Audits whether a verification (eval/metric/experiment/holdout) actually secures independent external ground truth, or whether the designer, the model, and the scorer are just confirming each other in a circle — via a 28-pattern taxonomy. Read-only. Use before trusting any 'how we'll know it worked' — A/B tests…
review
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".