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 hyxnj666-creator/ai-memory --skill ai-memory-system-architecturegit clone --depth 1 https://github.com/hyxnj666-creator/ai-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/hyxnj666-creator/ai-memory/ai-memory-system-architecture)<a href="https://agentmods.dev/skills/hyxnj666-creator/ai-memory/ai-memory-system-architecture"><img src="https://agentmods.dev/badge/skills/hyxnj666-creator/ai-memory/ai-memory-system-architecture/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/hyxnj666-creator/ai-memory/ai-memory-system-architecture"><img src="https://agentmods.dev/badge/skills/hyxnj666-creator/ai-memory/ai-memory-system-architecture.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.00046 | $0.00283 |
| Opus 5 | $0.00023 | $0.00142 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
ai-memory-system-architecture 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
System Architecture
Auto-generated by ai-memory from AI chat history. Edit memories via
ai-memory list/extract/resolverather than this file — it is fully regenerated on everyai-memory rules --target skills.
Event sourcing for the billing audit log
The billing domain becomes event-sourced. The source of truth is an append-only billing_events Postgres table (InvoiceCreated, LineItemAdjusted, PaymentCaptured, etc.), each row carrying a SHA-256 hash chain over (prev_hash, payload, timestamp). The current invoices table becomes a read-side projection rebuilt from the log. The rest of the app stays on the existing CRUD model — only billing needs this.
Why: Event sourcing answers compliance directly: every state change is a first-class, immutable record. Hash-chaining provides tamper evidence without an external service. Scoping to billing keeps the operational cost contained.
Rejected: Shadow-table journaling rejected — couples write-side logic to bookkeeping and does not give tamper evidence. External audit-log service rejected — added vendor cost without measurable gain over an in-database hash chain.
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 · 17 lines · 46 tokens per session scan A f9b346ac3c6d
ai-memory-system-architecture is a skill published in the GitHub repository hyxnj666-creator/ai-memory (43 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 283 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 skills, from other repositories
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
73
Sign-off - end-of-session checklist. Confirms it's safe to end, surfaces open action items, and writes the session's learnings back to memory and the KB so the workspace grows. Triggers on '/73', 'signing off', 'wrap up the session', 'end of session', 'that's a wrap'.
shared-agents-knowledge
Sync and use the shared-agents repo (team skills, rules + learnings). Use at session start, when loading team knowledge, searching learnings, or when the user mentions shared-agents, shared learnings, or team knowledge.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…