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 agentmods add skills/toejough/engram/curatenpx skills add toejough/engram --skill curategit clone --depth 1 https://github.com/toejough/engramWhat 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 | $0.00099 | $0.01338 |
| Opus 5 | $0.00049 | $0.00669 |
| Sonnet 5 | $0.00020 | $0.00268 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
curate 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curate — Judge Pending Offers Against the Host Vault
A served engram learn/engram amend write lands as a pending offer: a real note file,
marked pending: true, that hasn't yet been reviewed against the vault's existing (non-pending)
notes. Curation is that review — the same agent-judged covered/near/absent reasoning recall's
Step 2.5 performs against query candidates, applied instead to a pending offer against the host
vault's existing notes.
Host-local only, on your own initiative. engram serve's only job on a write is authenticate,
stamp identity, persist the pending marker, respond — judgment happens later, off the request
path, never synchronously inside the HTTP request that created the offer. Invoke this skill
reactively, whenever you notice one of the three surfacing signals (query payload flag, update
notice, write-path nudge), or whenever explicitly asked to curate.
Step 1 — Find pending offers
engram query excludes pending offers from its results by design — it can only tell you THAT some
exist (pending_offers: true in its payload), not which ones. There is no CLI listing for them
(engram count --group-by pending only counts). Scan the vault directly instead:
grep -l '^pending: true$' <vault>/*.md
Read each match in full (frontmatter + body) — that's the offer's claim.
Step 2 — Judge each offer against the host vault's existing notes
engram query --phrase "<offer's situation>" finds related existing notes the normal way (it
already excludes offers, so every result is a real candidate to judge against). For each offer:
| Outcome | Criterion | Action |
|---|---|---|
| Covered | an existing note already states the offer's claim, no material omission | reinforce it: engram amend --target <existing> --activate --chunk-source <ids> (carry forward any chunk-source the offer already had) [--supersedes ... if it corrects a different, outdated note] — then discard the offer: engram amend --target <offer> --discard |
| Near | overlaps an existing note's topic but adds ≥1 substantive claim the existing note omits | fold the new claim in: engram amend --target <existing> --chunk-source <ids> --subject/--predicate/--object (or --behavior/--impact/--action) [--supersedes ... if correcting] — then discard the now-redundant offer: engram amend --target <offer> --discard |
| Absent | no existing note addresses the offer's situation | accept as-is, clear its own marker: engram amend --target <offer> --clear-pending |
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 First seen · 84 lines · 99 tokens per session scan A 692ec5f5be46
curate is a skill published in the GitHub repository toejough/engram (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,338 once invoked, about $0.0005 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-31.
Other skills, from other repositories
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
lazarus-group
Adversary-emulation profile for Lazarus Group (G0032, aka Hidden Cobra / Diamond Sleet / Labyrinth Chollima), a North Korean RGB-linked actor conducting espionage, destructive, and financially motivated operations.
sidewinder-rattlesnake
Adversary-emulation profile for SideWinder (G0121 / Rattlesnake / T-APT-04 / Razor Tiger), India's suspected state-sponsored cyber-espionage actor.