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/stoa-platform/stoa/memory-consolidatenpx skills add stoa-platform/stoa --skill memory-consolidategit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/memory-consolidate)<a href="https://agentmods.dev/skills/stoa-platform/stoa/memory-consolidate"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/memory-consolidate.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00741 |
| Opus 5 | $0.00015 | $0.00370 |
| Sonnet 5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
memory-consolidate 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Consolidation — autoDream Pattern
CAB-2005: Inspired by Claude Code's autoDream process revealed in the March 2026 source leak.
During idle periods, autoDream merges disparate observations, removes logical contradictions,
and converts vague insights into verified facts.
This skill performs the same operation on STOA's memory system.
Step 1: Read All Memory Files
Read the memory index and all referenced topic files:
~/.claude/projects/-Users-torpedo-hlfh-repos-stoa/memory/MEMORY.md(index)- All
.mdfiles referenced in MEMORY.md (topic files) memory.md(project root — session state)
Step 2: Verify File References
For each file path mentioned in any memory file (backtick-quoted paths like path/to/file.ext):
- Check if the file still exists in the codebase
- If NOT: flag as stale, note the memory file and line
- If YES but content has changed significantly: flag as potentially outdated
Use Glob and Grep to verify existence. Do NOT read every referenced file — just check existence.
Step 3: Detect Contradictions
Scan for contradictions across memory files:
- Version conflicts: e.g., "ADR numbering: next ADR-048" in one file vs "ADR-060" in another
- Status conflicts: item marked DONE in one file but IN PROGRESS in another
- Port/URL conflicts: different ports or URLs for the same service
- Date conflicts: timeline inconsistencies
Step 4: Detect Stale Facts
Flag facts that are likely outdated:
- References to cycles older than 2 cycles ago still marked "CURRENT"
- TODO items with dates more than 2 weeks in the past
- "Active" items that haven't been updated in 30+ days
- Infrastructure references (IPs, service names) that may have changed
Step 5: Apply Fixes
For each issue found:
- Stale path: Remove or update the reference
- Contradiction: Keep the more recent/accurate version, remove the other
- Outdated fact: Update if current state is clear, otherwise flag for human review
- Stale TODO: Move to completed or remove if no longer relevant
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.
- 5d ago First seen · 82 lines · 30 tokens per session scan A 22bf2ea1723d
memory-consolidate is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 741 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-31.
Other skills, from other repositories
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
github
GitHub operations via the gh CLI.