Engram is a local or cloud-backed memory system for AI coding agents, provided as a single Go binary with SQLite full-text search and interfaces including a command line, HTTP API, MCP server, and terminal UI. It helps compatible coding agents retain project decisions, bugs, conventions, and other useful context across sessions. The catalogue add-ons configure and operate Engram’s memory workflows.
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.
npx skills add Gentleman-Programming/engram --skill backlog-triagegit clone --depth 1 https://github.com/Gentleman-Programming/engramWrote 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/gentleman-programming/engram/backlog-triage)<a href="https://agentmods.dev/skills/gentleman-programming/engram/backlog-triage"><img src="https://agentmods.dev/badge/skills/gentleman-programming/engram/backlog-triage/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/gentleman-programming/engram/backlog-triage"><img src="https://agentmods.dev/badge/skills/gentleman-programming/engram/backlog-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 145 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00075 | $0.03068 |
| Opus 5.5 | $0.00030 | $0.01227 |
| Sonnet 5.5 | $0.00015 | $0.00614 |
| Haiku 4.5 | $0.00007 | $0.00307 |
Grade A, and why
engram-backlog-triage 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when:
- Running a full backlog audit on Engram (or any repo)
- Deciding merge / request-changes / close / needs-design / approve-issue
- Cleaning noise from the issue tracker
- Prioritizing what to act on next
Maintainer Philosophy (Engram)
These are the non-negotiable product values. Every triage decision is filtered through them.
| Principle | What it means in practice |
|---|---|
| Zero-config | Works out of the box. No required flags, env vars, or setup beyond install. |
| Local-first | Data lives in ~/.engram/engram.db. No cloud dependency by default. |
| Single binary | One engram binary. No daemon, no service, no secondary processes needed. |
| Terminal-first | CLI and TUI are the primary UX. No web dashboard, no Electron. |
| Thin adapters | Plugin scripts (Claude, OpenCode, Gemini, Codex) are thin shims — logic lives in Go core. |
| Issue-first | Every PR must link a status:approved issue. No approved issue → no PR. |
| Evidence-based reviews | Request changes with specific, actionable items. No vague "needs improvement". |
| Tight scope | Reject features that expand Engram's surface area without a compelling case. |
| Small focused contributions | Prefer 50-line PRs solving one problem over 500-line PRs solving five. |
| Reject vague/scope-breaking work | Close scope-creep issues and PRs that turn Engram into something else. |
Disposition Classification
Assign exactly ONE disposition to each issue or PR:
| Disposition | When to use |
|---|---|
| MERGE | PR is correct, scoped, tests pass, linked approved issue. Merge immediately. |
| REQUEST CHANGES | PR has the right idea but needs specific fixes. List each item. |
| CLOSE | Noise, confirmed duplicate, vague/scope-breaking work, or obsolete work after maintainer review; missing approval/ownership alone requires remediation before merge. |
| NEEDS DESIGN | Idea is valid but architectural decision required before any PR is welcome. Open discussion or design issue first. |
| APPROVE ISSUE | Maintainer accepted proportional evidence per CONTRIBUTING.md; bugs include current-main SHA, reproduction, root cause, and regression test plan. Replace the current status with status:approved. |
| REJECT ISSUE | Vague, duplicate, scope-breaking, or belongs in Discussions. Close with explanation. |
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.
- 2d ago Changed · +3 lines 4d1c67b8dbd7
- 1mo ago First seen · 272 lines · 75 tokens per session scan A 9c7020ab3df0
engram-backlog-triage is a skill published in the GitHub repository Gentleman-Programming/engram (7,360 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 3,068 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…