project

project is a command for Claude Code from RohiRIK/OpenLtm. It costs 31 tokens per session (976 once invoked), scanned B, original, MIT.

A set of commands for managing a project’s goal and background information in a long-term context system. It can initialize, analyze, or register a project.

In plain words
What is it for?
Use it to record a project goal, analyze context for a task, or connect a project name with its folder.
Why use it?
It keeps project context available before work begins, so an agent can understand the goal and project setup without relying only on the current conversation.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the openltm plugin — 6 skills, 8 commands, 2 agents, 6 hooks shipped together

Good fit Use it to record a project goal, analyze context for a task, or connect a project name with its folder.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rohirik/openltm/project
Install

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.

Clone the repo
git clone --depth 1 https://github.com/RohiRIK/OpenLtm

Made for: Claude Code.

Or install openltm, the plugin that ships this one along with the rest of its 6 skills, 8 commands, 2 agents, 6 hooks.

Wrote 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.

agentmods badge for project

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohirik/openltm/project/github.svg)](https://agentmods.dev/commands/rohirik/openltm/project)
Your own site
<a href="https://agentmods.dev/commands/rohirik/openltm/project"><img src="https://agentmods.dev/badge/commands/rohirik/openltm/project/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.

agentmods 80×15 button for project

Your own site · 80×15
<a href="https://agentmods.dev/commands/rohirik/openltm/project"><img src="https://agentmods.dev/badge/commands/rohirik/openltm/project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 976 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00976
Opus 5.5 $0.00012 $0.00390
Sonnet 5.5 $0.00006 $0.00195
Haiku 4.5 $0.00003 $0.00098

Measured 9d ago against content hash cf182297af26, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 9d 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.

**Step 3 — Read registry:** `cat "${LTM_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}/projects/registry.json"` (treat missing as `{}`). Legacy installs may also have `~/.claude/projects/registry.json`; its entries are still read, but
commands/project.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 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

The project defaults to the current one (resolved from the working directory). To give it a friendly name first, run /openltm:project register.

1 — Check for an existing goal:

Call mcp__plugin_openltm_memory__context_items with { type: "goal" }. If a goal exists, show it and ask: "Replace it?"

2 — Ask for the goal:

"What is the current goal for <project>? (1–3 bullets, max 100 chars each)"

3 — Write:

Call mcp__plugin_openltm_memory__context_add with { type: "goal", content: "<goal>" }. A new goal replaces the previous one.

4 — 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 defaults to the current project; pass it only to look at a different one.

Returns: globals (importance ≥ 4) + scoped (importance ≥ 3).

2 — Search relevant memories: Call mcp__plugin_openltm_memory__recall(query="<topic>").

3 — Synthesize: Note any decisions, gotchas, or patterns relevant to the user's request.

4 — Proceed: Use the gathered context to inform your work. Quote relevant past decisions in your response.

Output format:

## Context Analysis — <project>

### Project State
- Goals: [from context scoped]
- Active Decisions: [from context globals]

### Relevant Memories
- [id] <memory> [category]

### Synthesis
<your summary of how this relates to prior work>

Read the full file on GitHub · 118 lines

Changes

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.

  1. 9d ago Changed · -17 lines cf182297af26
  2. 1mo ago First seen · 135 lines · 31 tokens per session scan B ae8d7f1d0b4b

Subscribe to this mod's changes

project is a command published in the GitHub repository RohiRIK/OpenLtm (28 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 976 once invoked, about $0.0001 per session on Opus 5.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.