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/holetron-lab/fleet-memory/hindsight-localnpx skills add Holetron-lab/fleet-memory --skill hindsight-localgit clone --depth 1 https://github.com/Holetron-lab/fleet-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/holetron-lab/fleet-memory/hindsight-local)<a href="https://agentmods.dev/skills/holetron-lab/fleet-memory/hindsight-local"><img src="https://agentmods.dev/badge/skills/holetron-lab/fleet-memory/hindsight-local.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.1 | $0.00032 | $0.01006 |
| Opus 5 | $0.00016 | $0.00503 |
| Sonnet 5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
hindsight-local 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.
This is a copy
100% identical to hindsight-local — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hindsight Memory Skill (Local)
You have persistent memory via the hindsight-embed CLI. Proactively store learnings and recall context to provide better assistance.
Setup Check (First-Time Only)
Before using memory commands, verify Hindsight is configured:
uvx hindsight-embed daemon status
If this fails or shows "not configured", run the interactive setup:
uvx hindsight-embed configure
This will prompt for an LLM provider and API key. After setup, the commands below will work.
How Hindsight Works
When you call retain, Hindsight does not store the string as-is. The server runs an internal pipeline that:
- Extracts structured facts from the content using an LLM
- Identifies entities (people, tools, concepts) and links related facts
- Builds temporal and causal relationships between facts
- Generates embeddings for semantic search
This means you should pass rich, full-context content — the server is better at extracting what matters than a pre-summarized string. Your job is to decide when to store, not what to extract.
Commands
Store a memory
Use memory retain to store what you learn. Pass the full context — raw observations, session notes, conversation excerpts, or detailed descriptions:
uvx hindsight-embed memory retain default "User is working on a TypeScript project. They enabled strict mode and prefer explicit type annotations over inference."
uvx hindsight-embed memory retain default "Ran the test suite with NODE_ENV=test. Tests pass. Without NODE_ENV=test, the suite fails with a missing config error." --context procedures
uvx hindsight-embed memory retain default "Build failed on Node 18 with error 'ERR_UNSUPPORTED_ESM_URL_SCHEME'. Switched to Node 20 and build succeeded." --context learnings
You can also pass a raw conversation transcript with timestamps:
uvx hindsight-embed memory retain default "[2026-03-16T10:12:03] User: The auth tests keep failing on CI but pass locally. Any idea?
[2026-03-16T10:12:45] Assistant: Let me check the CI logs. Looks like the tests are running without the TEST_DATABASE_URL env var set — they fall back to the production DB URL and hit a connection timeout.
[2026-03-16T10:13:20] User: Ah right, I never added that to the CI secrets. Adding it now.
[2026-03-16T10:15:02] User: That fixed it. All green now." --context learnings
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 · 112 lines · 32 tokens per session scan A a7cda72a99fe
hindsight-local is a skill published in the GitHub repository Holetron-lab/fleet-memory (0 stars, last pushed 8d ago), licensed MIT. It adds 32 tokens to every session and 1,006 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hindsight-local, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.