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 commands/rohirik/openltm/projectgit clone --depth 1 https://github.com/RohiRIK/OpenLtmWhat 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.00031 | $0.01002 |
| Opus 5 | $0.00015 | $0.00501 |
| Sonnet 5 | $0.00006 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade B, and why
project scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/projects/registry.json How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parse the first word of the arguments as <subcommand>. Pass remaining words as <args>.
If no subcommand given, show:
Usage: /openltm:project <subcommand>
init — seed a new project goal into the LTM context system
/openltm:project init
analyze — analyze project context before starting work
/openltm:project analyze [topic or task description]
register — register or rename a project in the LTM registry
/openltm:project register [name] [path]
init
1 — Verify project is registered:
cat ~/.claude/projects/registry.json
Match cwd. If missing, run /openltm:project register first.
2 — Check for existing goal:
bun --eval "
import { Database } from 'bun:sqlite';
const db = new Database(process.env.LTM_DB_PATH);
const row = db.query(\"SELECT content FROM context_items WHERE project_name=? AND type='goal' LIMIT 1\").get('<project>');
console.log(row ? row.content : '');
"
If a goal exists, show it and ask: "Replace it?"
3 — Ask for the goal:
"What is the current goal for <project>? (1–3 bullets, max 100 chars each)"
4 — Write:
bun --eval "
import { Database } from 'bun:sqlite';
const db = new Database(process.env.LTM_DB_PATH);
db.run(\"DELETE FROM context_items WHERE project_name=? AND type='goal'\", ['<project>']);
db.run('INSERT INTO context_items (project_name, type, content, created_at) VALUES (?, ?, ?, datetime(\"now\"))', ['<project>', 'goal', '<goal>']);
console.log('done');
"
5 — Confirm:
Project **<project>** seeded.
Goal: <goal>
Decisions, progress, and gotchas accumulate automatically via hooks.
Do NOT create context-goals.md or similar files. DB is the source of truth.
analyze
This command orchestrates context retrieval in the right order.
1 — Get project context:
Call mcp__plugin_openltm_memory__context(project="<project>").
Returns: globals (importance ≥ 4) + scoped (importance ≥ 3).
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.
- 2d ago First seen · 135 lines · 31 tokens per session scan B ae8d7f1d0b4b
project is a command published in the GitHub repository RohiRIK/OpenLtm (26 stars, last pushed 24d ago), licensed MIT. It adds 31 tokens to every session and 1,002 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).