More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    entergram

    2

    Persistent engineering memory for AI agents to store and query architectural decisions, conventions, and pitfalls.

    $5

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned
    entergram

    entergram

    Example session with this skill installed

    I need to modify the webhook signature verification. Is there any historical context on why we use this specific implementation?

    • Read your context and instructions
    • Compiled the entergram

    I queried the Entergram memory for "webhook signature verification" and found one relevant historical decision.

    Engineering Memory Recall

    IDCategoryFact/DecisionRationaleStatus
    cell_8f2dInfrastructureWebhook handlers must verify signatures before parsing JSON payloads.Prevents ReDoS attacks and unauthorized resource consumption from unauthenticated malformed payloads.Reviewed
    cell_a2c3SecurityUse the crypto.timingSafeEqual for secret comparison.Native string comparison in the previous version was vulnerable to side-channel timing attacks.Reviewed

    Next steps

    1. Check src/middleware/auth.ts to ensure the raw body is still accessible for signature verification before body-parsing middleware.
    2. Verify that your planned changes maintain the timing-safe comparison logic.
    3. If you optimize the verification flow, run get-entergram remember to document any new performance constraints.
    $5/mo

    Subscription · always the latest version

    • Secure checkout via Stripe
    • Cancel anytime
    • Delivered live via MCP

    About this skill

    AI agents often lack the historical context of why a codebase was built a certain way, leading to regressive changes and broken conventions. This skill provides a persistent engineering memory layer that stores architectural decisions, pitfalls, and rationale directly in your repository.

    What it does

    • Persistent memory stores architectural decisions and engineering rationale in human-readable Markdown.
    • Contextual recall allows agents to query the memory store for specific conventions or past failure modes before starting work.
    • History ingestion extracts facts and candidate memories from Git history and existing documentation.
    • Workflow dispatch retrieves established procedures for complex tasks like releases or migrations.
    • Memory triage provides a review workflow to verify or reject automatically extracted facts.

    How it works

    1. Initialize the repository memory using get-entergram init to scaffold the local storage.
    2. Ingest context from Git history and docs with the learn command to build an initial knowledge base.
    3. Query via MCP by connecting the agent to the Entergram server for real-time memory retrieval during coding tasks.
    4. Capture knowledge using the remember tool to persist new decisions, gotchas, or invariants discovered during a session.

    Frameworks & tools

    This skill interfaces with the Entergram CLI and MCP server. It supports indexing local repositories and integrates with MCP-compatible agents like Claude Code, Cursor, and Windsurf. Data is stored in Markdown with a SQLite search cache.

    Why this beats prompting it yourself

    Manual prompting relies on the agent's limited context window and lacks access to the "why" behind historical commits. This tool provides a dedicated, queryable index of engineering intent that survives across sessions and different agents.

    Use cases

    • Onboarding agents to unfamiliar codebases by providing an architectural overview and known pitfalls.
    • Validating changes against historical decisions to prevent recurring bugs or convention violations.
    • Documenting rationale for non-obvious implementation details directly during the development flow.
    • Standardizing procedures by retrieving "how-to" guides for infrequent but critical engineering tasks.

    Known limitations

    Memory can become stale if not updated following a change; always verify recalled facts against the current source code. Does not support remote synchronization or secrets storage.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires local Entergram CLI installation. Memory may become stale; must verify against current code. No support for storing secrets or remote sync.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    Entergram provides a persistent "memory layer" that stores the rationale and architectural decisions behind your code, preventing agents from making regressive changes or violating established conventions that aren't obvious from the source code alone.

    This skill is designed for MCP-compatible environments and works seamlessly with advanced AI coding tools like Claude Code, Cursor, and Windsurf by connecting them to a local SQLite-backed knowledge base.

    Setup is straightforward: use the `init` command to scaffold your storage, then run the `learn` command to automatically ingest context from your Git history and existing documentation.

    All architectural decisions and memories are stored in human-readable Markdown files directly within your repository, ensuring you maintain full ownership and can version-control your engineering knowledge alongside your code.

    While the tool can automatically extract facts, it includes a "memory triage" workflow that allows you to review, verify, or reject information to ensure the agent's knowledge remains accurate and high-quality.

    You receive the Entergram CLI and MCP server integration, enabling your agents to query, store, and manage architectural context across any local repository you initialize.

    New in Agents & Orchestration