engram-ui-elements

A set of rules for building Engram dashboard pages and interface parts such as cards, tables, metrics, lists, and detail views.

In plain words
What is it for?
Use it when adding or changing dashboard pages, browsing flows, or components that connect projects, sessions, observations, and their details.
Why use it?
It keeps related information connected and makes empty states, metrics, controls, and navigation clearer and more useful.

Skill for Claude CodeCodex

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 skills/gentleman-programming/engram/ui-elements
Any agent
npx skills add Gentleman-Programming/engram --skill ui-elements
Clone the repo
git clone --depth 1 https://github.com/Gentleman-Programming/engram

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 248 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.00036 $0.00248
Opus 5 $0.00018 $0.00124
Sonnet 5 $0.00007 $0.00050
Haiku 4.5 $0.00004 $0.00025

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

Security

Grade A, and why

engram-ui-elements 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.

skills/ui-elements/SKILL.md · 37 lines

What it actually says

When to Use

Use this skill when:

  • Adding a new page or partial to the dashboard
  • Creating cards, metrics, tables, lists, or detail views
  • Designing connected navigation between related entities

UX Rules

  1. Every list item should lead somewhere useful when domain relationships exist.
  2. Prefer connected flows: project -> session -> observation -> full detail.
  3. Empty states must explain what is missing and what unlocks data.
  4. Metrics must reflect real system state, not decorative counters.
  5. Detail pages should show metadata, content, and the next relevant links.

Composition Rules

  • Use metrics for orientation, not for replacing core content.
  • Use cards for browsable entities and tables for dense comparative admin data.
  • Avoid nested framed boxes unless they communicate a hierarchy the user needs.
  • Keep action controls close to the entity they affect.
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 · 37 lines · 36 tokens per session scan A 1ec7a5c10c86

Subscribe to this mod's changes

engram-ui-elements is a skill published in the GitHub repository Gentleman-Programming/engram (6,232 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 248 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens