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 skills/criterium/opencode-lab/memory-systemnpx skills add criterium/opencode-lab --skill memory-systemgit clone --depth 1 https://github.com/criterium/opencode-labWhat 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.00000 | $0.05504 |
| Opus 5 | $0.00000 | $0.02752 |
| Sonnet 5 | $0.00000 | $0.01101 |
| Haiku 4.5 | $0.00000 | $0.00550 |
Grade A, and why
memory-system 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory System — editing rules
Loaded by custom.md upon receiving >> or <<. Single file per scope (memory.md)
that accumulates relevant project information.
In effect until the skill is loaded again. Apply the certainty rule without asking.
Terminology
- memory-system or m-s: memory files of the scope managed by this skill:
memory.md,memory/*.md,todo.md,checkpoint.md.sessions.mdis an optional historical record, not included.
Source of truth
The definitive source of truth is codebase + database. Memory describes, code executes. Any claim in memory about files, symbols, data structures or schemas must be verifiable against the code on disk. If memory and code disagree, code prevails. The model decides how and what to verify based on context and available tools (grep, glob, DFM parsing).
Division principle
memory.mdself-contained for initial orientation: critical rules, context, map. An agent without context must be able to start with<< ./and understand the project.memory/*.mdis on-demand deepening: implementation detail, specific references. Loaded only when the task requires them.- The index of
memory.mdmust include a column indicating for which type of task to load each file frommemory/. todo.md: pending tasks.<<shows it.>> <scope> checkreports status. Written via>> <scope> todo <content>or manually.
Writing principle
Any content under this skill must prioritize precision and effectiveness over verbosity or human-oriented explanations. Prefer: imperative over descriptive, concrete examples over generalities, direct references over introductions. No politeness, narrative or justifications. Compactness is a consequence, not a goal — do not sacrifice clarity for brevity.
Verification criteria:
- (a) Unambiguous. In what is stated, not in what is omitted. Uncertainty is declared, not hidden in vague wording.
- (b) Action, not description. For instructions and prompts: what to do, not what each thing is. Conditions, preconditions and guard clauses are part of the instruction.
- (c) Action precedes reason. For instructions and prompts: the what before the why.
- (d) No fossils. Do not include implementation dates, versions ("since X"), or counts that expire ("17 forms"). Current state describes how things are, not when they changed. The temporal delta belongs to git / sessions.md.
- (e) Compact by default. One idea = one paragraph. Tables for relatable data. If something is explained in one line, do not expand it to three.
- (f) Relevant. Only what an agent would lose without help deserves memory. Do not store: obvious code structure, standard framework patterns, available official documentation, or conventions inferable from project context.
- (g) Fresh and actionable. Information must be the latest available. If it describes code, verify the code still exists (files, functions, routes). If it describes a decision, it must be the current one. An entry unverified since creation is a review candidate. Prioritize: design decisions, undocumented workarounds, execution orders, non-obvious setup, context inferred from multiple sources.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 374 lines · 0 tokens per session scan A e753ac8cbbe0
memory-system is a skill published in the GitHub repository criterium/opencode-lab (44 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,504 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…