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 niels-emmer/myace --skill memory-systemgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/memory-system)<a href="https://agentmods.dev/skills/niels-emmer/myace/memory-system"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/memory-system/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/niels-emmer/myace/memory-system"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/memory-system.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.00031 | $0.00912 |
| Opus 5.5 | $0.00012 | $0.00365 |
| Sonnet 5.5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
A coding agent's context resets between sessions. Without a durable place to record decisions, conventions, and the reasoning behind them, every new session either re-derives context from scratch (slow, and prone to contradicting earlier decisions) or plows ahead without it (fast, and prone to redoing work or reversing a decision nobody remembers making). This skill defines a small, low-overhead file layout that fixes that, and the routine for keeping it current.
When to use it
At the start of every nontrivial task, before touching code. At the end of every nontrivial task, before considering it done. "Nontrivial" means: it involved a design or approach decision, it changed behavior a future session would need to know about, or it took more than a few minutes of back-and-forth to get right. A one-line typo fix doesn't need a memory update; a new feature, an architecture change, or a fix for a subtle bug does.
File layout
Create these under docs/memory/ in the project root the first time this skill is used on a project that doesn't have them yet:
docs/memory/core-principles.md— the stable layer. Architectural decisions and constraints that rarely change: the chosen stack, non-negotiable invariants, things that would require a real conversation to reverse. Keep this short — if it's growing every week, content belongs in one of the other files instead.docs/memory/workflow.md— the process layer. How this specific team/project actually works day to day: branching conventions, how releases happen, where things like migrations or config live, anything a new session needs to act consistently with existing practice. Changes more often than core-principles but still infrequently.docs/memory/decisions.md— the evidence/decision log. Append-only. Every nontrivial task adds one dated entry here. Never edit or delete a past entry to "clean it up" — if a decision was later reversed, add a new entry noting the reversal and why; the history is the point.
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.
- 1mo ago First seen · 43 lines · 31 tokens per session scan A 7569659077bf
Memory System is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 912 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-09-03.
Other skills, from other repositories
agent-experience
Make a code repository agent-ready with state-of-the-art AX (Agent Experience): audit and set up AGENTS.md / CLAUDE.md and agent docs, wire verification sensors with self-correction messages, and build docs-as-memory (architecture docs, ADRs, exec plans). Use when the user wants to make a repo agent-ready or…
idiomatic-go
Apply Go community idioms for API and package design, error and concurrency patterns, naming (initialisms, stutter, receivers), generics vs interfaces, and Go code review — including PR or diff review, questions about "the Go way", pointer vs value receivers, channels vs mutexes, and building Go language tooling…
eclipse-license-check
Vet third-party dependencies for an Eclipse Foundation project with the Eclipse Dash License Tool — license checks, "do I need to vet X?" questions, IPLab review filing, and release IP due diligence. Use whenever the user mentions Eclipse license checking, dash-licenses, the Dash License Tool, IPLab, third-party…
go-documentation
Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, doc.go, exported-symbol comments, testable Example functions, deprecation notices — and publish or debug modules on pkg.go.dev (pkgsite, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to…
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
domainmodel-dsl
Read, write, and modify Domain Model DSL files (.dmodel) — datatypes, entities with inheritance and multi-valued features, and nested packages with qualified cross-references. Use when the user wants to create, edit, explain, or debug a domain model in this DSL, including resolving references across packages.