setup

A setup command that connects a repository to Engram, a local project-knowledge system, and registers its MCP server. It also handles the required binary and repository configuration.

In plain words
What is it for?
Use it when preparing a repository for Engram's capture and session-brief features, then restart the coding-agent session so the tools appear.
Why use it?
It removes the manual work of installing Engram, ignoring its local files, and adding the server connection.

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/setup
Clone the repo
git clone --depth 1 https://github.com/techtheist/engram
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 401 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00024 $0.00401
Opus 5 $0.00012 $0.00200
Sonnet 5 $0.00005 $0.00080
Haiku 4.5 $0.00002 $0.00040

Measured yesterday against content hash 34651abab0da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

setup scanned grade C with 2 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 yesterday.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -fsSL https://raw.githubusercontent.com/techtheist/engram/main/install.sh | sh -s -- --bin-only

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://raw.githubusercontent.com/techtheist/engram/main/install.sh | sh -s -- --bin-only
claude-plugin/commands/setup.md · 25 lines

What it actually says

Wire the current repository to Engram. The plugin already provides the capture skill and the session-brief hook globally, so the only per-repo work is the binary and the MCP registration — never install a project-level skill or hook here.

  1. Binary. Check command -v engram-alpha. If missing, ask the user once for consent to install, then run:

    curl -fsSL https://raw.githubusercontent.com/techtheist/engram/main/install.sh | sh -s -- --bin-only
    

    (--bin-only matters: the installer's default repo wiring would duplicate what this plugin ships.) If they decline, stop and point them at https://github.com/techtheist/engram#install.

  2. Wire the repo. From the repository root:

    engram-alpha setup --cli claude --mcp-only
    

    This git-ignores .engram/ and writes the engram MCP server into .mcp.json (or prints the snippet if a foreign .mcp.json exists — apply it, .mcp.json holds machine-absolute paths, so keep it out of version control).

  3. Connect. Tell the user to restart the session (or approve the new MCP server via /mcp) so the engram tools appear. The next session opens pre-briefed via the plugin's SessionStart hook.

  4. Cold start. If this created a brand-new graph, mention that once connected, the skill offers a one-time seeding pass from the project's existing docs/history — and that /engram:pane opens the graph UI.

If anything fails, report the exact error — never pretend the repo is wired.

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. yesterday First seen · 25 lines · 24 tokens per session scan C 34651abab0da

Subscribe to this mod's changes

setup is a command published in the GitHub repository techtheist/engram (17 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 401 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.