pane

A command that opens the Engram graph pane, a local view of the project's stored coding decisions and notes.

In plain words
What is it for?
Opening the pane for a repository that already has an Engram graph and reporting its local URL or IDE panel location.
Why use it?
It handles checking or starting Engram's background service and avoids giving the user the wrong local address.

Command

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.

agentmods
npx agentmods add commands/techtheist/engram/pane
Clone the repo
git clone --depth 1 https://github.com/techtheist/engram
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00019 $0.00304
Opus 5 $0.00010 $0.00152
Sonnet 5 $0.00004 $0.00061
Haiku 4.5 $0.00002 $0.00030

Measured 2d ago against content hash f19ee342a981, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

claude-plugin/commands/pane.md · 17 lines

What it actually says

Get the Engram graph pane in front of the user.

  1. If .engram/daemon.json exists in the repo root, read its port and check http://127.0.0.1:<port>/health. If healthy, the pane is already up — one machine core serves every project (its health reports the home graph; that's normal, the pane's project switcher has this repo).
  2. Otherwise run, from the repository root:
    engram-alpha serve
    
    It makes sure the machine core is running (starting it detached if needed), registers this repo with it, prints the pane URL, and exits on its own — no backgrounding needed. Then re-read .engram/daemon.json for the real port (the default 8787 may have been taken).
  3. Tell the user the URL (http://127.0.0.1:<port>) — or, if they use the JetBrains plugin / VS Code extension, that the same pane lives in their IDE's Engram panel.

If the engram-alpha binary is missing, run /engram:setup first instead of improvising an install. If this repo has no .engram/ graph at all, say so — the pane of an unwired repo would be an empty graph.

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. 2d ago First seen · 17 lines · 19 tokens per session scan A f19ee342a981

Subscribe to this mod's changes

pane is a command published in the GitHub repository techtheist/engram (17 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 304 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-30.