Borrowing it
Nothing to install: this file belongs to JJHbrams/Project-AMBER. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JJHbrams/Project-AMBER/master/.github/skills/engram-connect/SKILL.mdgit clone --depth 1 https://github.com/JJHbrams/Project-AMBERWrote 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/skills/jjhbrams/project-amber/engram-connect)<a href="https://agentmods.dev/skills/jjhbrams/project-amber/engram-connect"><img src="https://agentmods.dev/badge/skills/jjhbrams/project-amber/engram-connect/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/skills/jjhbrams/project-amber/engram-connect"><img src="https://agentmods.dev/badge/skills/jjhbrams/project-amber/engram-connect.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.00022 | $0.00692 |
| Opus 5.5 | $0.00009 | $0.00277 |
| Sonnet 5.5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
engram-connect 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engram Connect
Use this only when Codex's Engram MCP tools are absent or connection recovery is requested. First inspect the configured Codex MCP entry and report what is missing. Never alter provider configuration or hook trust as part of a diagnosis.
For a direct, read-only MCP recovery probe, explicitly identify the Codex root and
run node scripts/engram-connect.mjs probe --root <Codex-root>. It reads only that
root's config.toml, accepts an unauthenticated http://127.0.0.1 or
http://localhost Engram URL, initializes Streamable HTTP MCP, and lists tools.
It never changes config, hooks, trust, headers, or provider state.
The only data calls are allowlisted and bounded:
node scripts/engram-connect.mjs search --root <Codex-root> --query <keywords>node scripts/engram-connect.mjs read-note --root <Codex-root> --id <note-id>
The helper rejects remote URLs, HTTPS, authorization/header configuration, unknown tools, oversized config/output, and malformed MCP responses. It sends no conversation content, credentials, raw memory, or arbitrary tool payloads.
If the service is reachable but tools remain unavailable, try the explicit live
reconnect below first when an existing managed daemon and its target thread are
available. Start a new Codex session only when that bounded reconnect is unsupported
or there is no such existing daemon/thread. Never add an automatic retry loop,
watchdog, or repeated reload polling.
Use engram-hook-trust separately for explicit /hooks review or a user-requested
restore; this skill never approves hooks.
Explicit live Codex reconnect
When the running Codex session itself is missing Engram tools, use the bounded reconnect command below. It attaches only to the already-running daemon through its control socket; it never starts an app-server, thread, or conversation, and never writes Codex configuration, hook trust, or approvals.
node scripts/engram-connect.mjs reconnect --root <CODEX_HOME> --thread-id <CODEX_THREAD_ID> --codex-executable <path-to-codex.exe>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · +28 lines 31c922d1516b
- 1mo ago First seen · 30 lines · 22 tokens per session scan A 6a779f5ecf91
engram-connect is a skill published in the GitHub repository JJHbrams/Project-AMBER (2 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 692 once invoked, about $0.0001 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-09-13.
Other skills, from other repositories
review-logs
Review Deus system health logs, show daily reports, surface pinned issues, and rotate old log files. Uses a local Ollama model to analyze errors and warnings.
memory-doctor
Run Locus environment health check — 10-point diagnostic covering Node.js version, storage backend, FTS5, DB permissions, git availability, and more. Use when troubleshooting plugin issues or checking setup.
customize
Add new capabilities or modify Deus behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.
troubleshoot
Diagnose and fix claude-mem installation issues. Checks worker status, database integrity, service health, dependencies, and provides automated fixes for common problems.
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
fix
A debugging workflow that investigates software bugs by turning a plain-language report into a small failing test, then comparing possible causes using evidence.