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.00628 |
| Opus 5 | $0.00017 | $0.00314 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 7d 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
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / memory-system
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Persistent Memory System (Cross-Session Context)
Purpose: Store distilled user preferences, project decisions, and feedback across sessions without token bloat.
🎯 Progressive Disclosure & L3 Reference Index
Read REQUIRED 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 structures, pruning algorithms, and frontmatter schemas | Saving new memory topics & index maintenance |
📁 1. Directory Structure & Pointer Format
.agent/memory/
├── MEMORY.md ← Lean pointer index (max 200 lines)
├── user-preferences.md ← Role, shell, communication style
├── project-conventions.md ← Tech stack, design tokens, architecture
└── tech-decisions.md ← ADR summaries and framework choices
Pointer Index Syntax (.agent/memory/MEMORY.md)
- [user] Prefers PowerShell 7 on Windows 11 → user-preferences.md
- [project] Zero hardcoded drive letters; strictly relative links → project-conventions.md
- [feedback] Deliver concise responses with comparison tables → feedback-history.md
🚫 2. Critical Memory Boundaries (Zero-Secrets Rule)
- NEVER Save Secrets: Never write API keys, private keys, passwords, or tokens to memory.
- Distilled Insights Only: Do not store entire raw conversation transcripts.
- No Dynamic Ephemeral State: Do not store transient PID numbers or temporary file paths.
🛠️ 3. Execution Cycle
1. TRIGGER ➔ User says "remember this" or architectural decision is finalized.
2. CATEGORIZE➔ Assign tag: [user], [project], [feedback], or [reference].
3. APPEND ➔ Write details to specific topic file; add 1-line pointer to MEMORY.md.
What ships with it
1 file 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.
- 7d 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 yesterday), licensed MIT. It adds 35 tokens to every session and 628 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-09-03.
Other skills, from other repositories
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.
context-layer-health-check
Semantic review of context wiki quality after deterministic consolidation.