relaxed

A local project memory system that stores decisions, their reasons, cautions, problems, solutions, insights, and open intentions in a connected knowledge graph. It lets later coding sessions recall why the project works the way it does.

In plain words
What is it for?
Use it at the start of a session to recall project context, search earlier decisions before making changes, and trace related reasoning or conflicts.
Why use it?
It reduces repeated investigation and prevents important reasoning from being lost between sessions or buried in chat history.

Agent

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 agents/techtheist/engram/relaxed
Clone the repo
git clone --depth 1 https://github.com/techtheist/engram
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,095 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod 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.00000 $0.01095
Opus 5 $0.00000 $0.00548
Sonnet 5 $0.00000 $0.00219
Haiku 4.5 $0.00000 $0.00110

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

Security

Grade A, and why

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

Origin

This is a copy

89% identical to aggressive — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/engram/agents/relaxed.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engram — durable project memory (MCP server: engram)

This project keeps a local, user-owned knowledge graph of its reasoning: Decisions and their reasons, Principles, Cautions that bit us, Problems and Resolutions, Insights, open Intents, Anchors that cluster them. Not code structure — the code holds that. What good capture buys: the next session starts already knowing why things are the way they are, and the user sees and curates everything in the pane.

Recall. Call the brief tool once at session start and read it before planning — unless the session already opens with an injected "# Engram brief" (a session-start hook provides it); then read that and skip the tool call. If the brief's first line says the session is bound by fallback — or it names a project that is not your workspace (a client that never answered MCP roots) — call brief again with project set to this workspace's ABSOLUTE path: it rebinds the session and returns the right project's brief. Before any non-trivial decision, search the graph; hits carry their 1-hop neighbors — read conflicts-with / replaces edges first, and pass parents/children to get_node when you need the reasoning chain. For history: timeline walks a node's replaces chain, audit pages the mutation journal. For whole-graph reviews or exports (a decisions.md), page list_nodes — complete nodes with full bodies; batch cleanups and multi-note captures go through update_nodes / add_notes. A hit marked stale: true has decayed trust: verify it before relying on it, and refresh it with update_node if it's still accurate.

Capture. Capture sparingly — only clearly durable, high-value knowledge: key Decisions with their reasons, stated Principles, hard-won Cautions, Problems with their Resolutions. A dozen good nodes beat fifty mirrored doc lines; when in doubt, don't write. Node type is one of exactly 9: Decision, Principle, Caution, Problem, Resolution, Insight, Intent, Anchor, Tombstone — a record that knowledge was deliberately removed; don't resurrect it (call describe_ontology if this graph runs a custom set). Write shapes: add_note {"type": "Decision", "title": "...", "body": "..."}; link {"from": "<id>", "to": "<id>", "type": "because"}; add_notes {"notes": [...]} items carry NO links — link the returned ids in a second pass. If describe_ontology lists custom fields, pass "fields": {"name": value} — refusals teach the roster; follow them. Connect notes with link using sentence-shaped edges (because / answers / about / builds-on / replaces / conflicts-with / needs; about targets Anchors only). Every write's response is a verdict, not a receipt: on {matched, created: false} merge into the match with update_node instead of duplicating; on warnings you are near contradicted or superseded canon — check it before piling on; on suspects the write queued unjudged look-alike pairs — judge each immediately with resolve_suspect (conflict | replaces | dismiss) and tell the user when one genuinely contradicts standing canon (the one exception to silent capture). When several notes share a subject, create/reuse an Anchor and attach them — anchors never accrue by themselves. Batch the writing at natural stopping points, never the noticing: every real decision gets captured unprompted — a feature request usually hides one (library picked, shape chosen, tradeoff accepted). Don't narrate writes. Never store secrets, credentials, or volatile implementation detail (line numbers, transient state).

Maintain. Judge the brief's suspected conflicts with resolve_suspect: contradiction → conflict; fresher restatement → replaces; complementary (a Resolution implementing an Intent) → dismiss, then ensure the answers edge exists. When a Resolution answers a Problem/Intent, also set that node's status to resolved. list_drift names nodes whose code_refs no longer exist: fix the paths via update_node and re-check the claim itself.

Trust. approve_node is restricted: only on the user's explicit demand, or after verifying a node's content word-by-word. Routine "still relevant" signals are update_node, never approval.

Read the full file on GitHub · 69 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. 2d ago First seen · 69 lines · 0 tokens per session scan A 33cd99d73066

Subscribe to this mod's changes

relaxed is an agent published in the GitHub repository techtheist/engram (17 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,095 tokens. A static security scan graded it A with 0 findings. It is 89% identical to aggressive, differing in 2 lines, and is treated as a copy.

Related

Other agents, from other repositories

tl-archivist

Specialist subagent for thoughtline memory hygiene. Use when asked to audit, deduplicate, prune, or reorganize memories — "clean up my memory", "find duplicates", "what's stale?", "auditá la base", "qué memorias podemos archivar?". Read-mostly, never deletes without explicit user confirmation.

AgusLoza2021/Thoughtline · 72 tokens

hyperledger-fabric-developer

Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.

davepoon/buildwithclaude · 63 tokens

legal-advisor

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.

davepoon/buildwithclaude · 49 tokens

agent-reviewer

Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.

guanyang/open-agent-hub · 21 tokens

00-session-bootstrap

Recover state from previous session including action cards, missed debriefs, and loop escalation.

assafkip/kipi-system · 21 tokens

dvalin-security

After changing code that handles input, authentication, authorization, secrets, queries, commands, templates, dependencies, or deployment configuration.

arthurpanhku/dvalincode · 0 tokens