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.
git clone --depth 1 https://github.com/RohiRIK/OpenLtmWrote 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/commands/rohirik/openltm/analyze-context)<a href="https://agentmods.dev/commands/rohirik/openltm/analyze-context"><img src="https://agentmods.dev/badge/commands/rohirik/openltm/analyze-context/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/commands/rohirik/openltm/analyze-context"><img src="https://agentmods.dev/badge/commands/rohirik/openltm/analyze-context.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00496 |
| Opus 5.5 | $0.00016 | $0.00198 |
| Sonnet 5.5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
analyze-context 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 6d 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
Pre-task context analysis. Orchestrates context retrieval in the correct order and synthesizes a brief.
Usage:
/openltm:analyze-context [topic]
Steps
1 — Resolve project name:
Use the project name shown in the injected SessionStart block (## LTM Session: <name>), or the repository directory name. context needs no name — it defaults to the current project; recall uses the name as a filter. If unsure, omit project on recall and search all projects.
2 — Load project context:
Call mcp__plugin_openltm_memory__context() — project defaults to the current project; pass it only to look at a different one.
Returns: globals (importance ≥ 4, all projects) + scoped (importance ≥ 3, this project only).
3 — Search relevant memories:
If a [topic] was given, call mcp__plugin_openltm_memory__recall(query="<topic>", project="<project>").
If no topic, call mcp__plugin_openltm_memory__recall(project="<project>", limit=5) to surface the top recent memories.
4 — Synthesize and present:
## Context Brief — <project>
### Project State
Goals: [from scoped context, type=goal]
Decisions: [from globals + scoped, category=architecture]
Gotchas: [from globals + scoped, category=gotcha]
### Relevant to "<topic>"
- [id] <memory content> [category, importance★]
...
### Summary
<1-3 sentence synthesis: what matters for this task, what to avoid, what prior decisions apply>
If no memories found: No prior context found — this looks like new territory.
This command is an alias for
/openltm:project analyze. For full project management (init, register), use/openltm:project.
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.
- 6d ago Changed d9c8a1842a7e
- 1mo ago First seen · 55 lines · 39 tokens per session scan A 112e063a8d99
analyze-context is a command published in the GitHub repository RohiRIK/OpenLtm (28 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 496 once invoked, about $0.0002 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-08-30.
Other commands, from other repositories
help
Get help with EverMem plugin setup and available commands.
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
memory-migrate
Migrate legacy .flow/memory/{pitfalls,conventions,decisions}.md flat files into the categorized YAML schema — host agent classifies each entry directly.
prime
Prime context for fresh session: /prime [task hint] [--quick] [--verbose].
warden-select
Measure pending token-warden candidate rules for an agent on the golden suite, evict or activate them, and recompile the agent's memory.
update
Sync tasks and refresh memory from your current activity.