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 DDS-Solutions/AI-TadPole-OS --skill memory-systemgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/memory-system)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/memory-system"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/memory-system"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/memory-system.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.00035 | $0.01502 |
| Opus 5.5 | $0.00014 | $0.00601 |
| Sonnet 5.5 | $0.00007 | $0.00300 |
| Haiku 4.5 | $0.00003 | $0.00150 |
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 9d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / memory-system
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Memory index bloat, broken topic pointers, or accidental credential leakage.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Persistent Cross-Session Memory System
Purpose: Store distilled user preferences, project conventions, and architectural decisions across sessions without context token bloat, ensuring instant cold-start alignment.
Workflow Bindings: Integrated into/onboardand/codify.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign memory rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/memory_schema_and_topic_templates.md |
Topic file schemas, 4-category taxonomy, and pruning algorithms | Creating new topic files & maintaining line ceilings |
scripts/memory_manager.py |
Automated pointer auditor, credential leak scanner, and entry recorder | Auditing memory health, verifying pointers, and adding entries |
MEMORY.md |
Active live Sovereign memory pointer index | Cold-start state restoration at session inception |
📁 1. Directory Structure & Pointer Architecture
.agent/memory/
├── MEMORY.md ← Lean pointer index (strictly capped at 200 lines)
├── user-preferences.md ← Role, shell, output style, and IDE preferences
├── project-conventions.md ← Tech stack, design tokens, architecture idioms
└── tech-decisions.md ← Compatibility status and Architectural Decision Records
What ships with it
2 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.
- 9d ago Changed · +50 lines b384851bf1e0
- 1mo ago First seen · 65 lines · 35 tokens per session scan A edfe07876b84
memory-system is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 1,502 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
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, resolving TinyBase import paths, configuring browser or database…
optimizing-clickhouse-and-hogql-queries
Workflow for optimizing ClickHouse and HogQL queries. Use when a HogQL query, query runner, insight, or report is too slow; when a hand-written ClickHouse query (via syncexecute or in a migration) is too slow; when ClickHouse times out or hits memory limits; when investigating a slow system.querylog row; or when…
generating-clickhouse-query-performance-reports
Produce and structure slow-query performance reports for PostHog's production ClickHouse (US and EU). Use when asked for a slow query report, query performance analysis over the last N days, per-team query cost, OOM or timeout investigation, cluster cost/memory regressions, or materialization candidates. Covers the…
query-clickhouse-via-metabase
Run ClickHouse system.querylog analysis via the internal Metabase API. Use when investigating slow queries, materialization candidates, per-team query performance, ClickHouse cost or memory issues, or any system.querylog question. Covers prod-us and prod-eu, SSO-gated cookie auth via hogli, and ready-to-run query…
context-layer-dreaming
Synthesizes recent organizational activity into a durable context wiki. Use when running a nightly or incremental context-layer dream, or when updating sourced organizational context from completed work.
context-layer-consolidation
Keep the context wiki coherent using the deterministic lint report queue.