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/tc407-api/titan-memory/statusnpx skills add TC407-api/Titan-Memory --skill statusgit clone --depth 1 https://github.com/TC407-api/Titan-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/tc407-api/titan-memory/status)<a href="https://agentmods.dev/skills/tc407-api/titan-memory/status"><img src="https://agentmods.dev/badge/skills/tc407-api/titan-memory/status.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.00017 | $0.00294 |
| Opus 5 | $0.00009 | $0.00147 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
status 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 3d 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
Titan Memory Status
Run a comprehensive health check on Titan Memory and report results.
Steps
- Get core stats by calling
titan_stats - Get MIRAS stats by calling
titan_miras_stats - Get NOOP stats by calling
titan_noop_stats
Report Format
Present a clean status report:
Titan Memory v2.1.0 — Status Report
====================================
Layers:
Factual (L2): XX memories
Long-term (L3): XX memories
Semantic (L4): XX memories
Episodic (L5): XX memories
Total: XX memories
MIRAS Enhancements:
Embedding: [active/inactive]
Highlighting: [active/inactive]
Surprise Filter: [active/inactive]
Decay: [active/inactive]
Cross-Project: [active/inactive]
LLM Turbo Layer: [enabled/disabled]
Memory Hygiene:
Writes today: XX
NOOPs today: XX
Write ratio: XX%
Status: [HEALTHY / DEGRADED / ERROR]
If any component shows errors, suggest fixes.
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.
- 3d ago First seen · 50 lines · 17 tokens per session scan A 9d159400ef61
status is a skill published in the GitHub repository TC407-api/Titan-Memory (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 17 tokens to every session and 294 once invoked, about $0.0001 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
uteke-memory
Persistent memory engine for AI agents via the uteke CLI — remember, recall, search, forget with semantic + FTS5 hybrid search, documents, knowledge graph, rooms, tiered memory, and multi-agent namespaces.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
alive:search-world
The human needs something that exists somewhere in the world but they don't know where. A decision, a person, a file, a reference — it's been captured, they just can't find it. Searches decisions, people, files, references, insights, and log history across all walnuts in priority order.
alive-capture
Capture external content into a walnut bundle -- emails, transcripts, screenshots, documents, research.