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/opencoven/coven/memory-recallnpx skills add OpenCoven/coven --skill memory-recallgit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/memory-recall)<a href="https://agentmods.dev/skills/opencoven/coven/memory-recall"><img src="https://agentmods.dev/badge/skills/opencoven/coven/memory-recall.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00043 | $0.01692 |
| Opus 5 | $0.00022 | $0.00846 |
| Sonnet 5 | $0.00009 | $0.00338 |
| Haiku 4.5 | $0.00004 | $0.00169 |
Grade A, and why
memory-recall scanned grade A with 1 finding 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 5d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`execve`/`subprocess.run(["coven-memory", "search", "--familiar", familiar, How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Recall
Retrieval-side contract for the Coven memory layer (Authoritative Plan v1 hole #7;
bead cmem-pbr). Any familiar, under any runtime, uses this skill to pull
already-promoted facts back into working context. It does not write, promote,
or mutate anything under ~/.coven/memory — that is the promotion layer's job
(coven memory promote, schema: familiar-contract/schemas/coven-memory-schema.md §11).
When to use
- The question depends on a promoted Coven fact, decision, or cross-familiar context rather than the current session or the familiar's own MEMORY.md.
- "Did we decide X?" / "what did attest about Y?" for anything that plausibly predates the current session or originated with another familiar.
- As a supplement to the runtime's own memory search (which covers per-familiar MEMORY.md / daily notes / transcripts). Recall covers the layer below that: promoted, attested, cross-familiar-visible.
When NOT to use
- Answer is in the current session → just answer.
- Answer is in the familiar's own MEMORY.md or daily files → use the runtime's memory tools.
- The promotion layer has not run for the relevant window → recall returns empty; say so honestly. Never fabricate a hit.
Inputs
| Field | Type | Required | Description |
|---|---|---|---|
query |
string | ✅ | Natural-language question or keyword phrase. |
familiar |
string | ❌ | Store scope filter passed to the crate: coven (default; the shared store) or a familiar id for per-familiar stores. Must match ^[A-Za-z0-9_-]{1,128}$ — the same shape the crate's own validate_identifier enforces for familiar_id. |
k |
int | ❌ | Max results. Default 5, max 20. |
since / until |
ISO date | ❌ | Filter on manifest timestamp. |
verified_only |
bool | ❌ | Default true. Drop hits whose manifest sha256 no longer matches the promoted snapshot or whose attested_via file is missing. |
Outputs
| Field | Type | Description |
|---|---|---|
hits |
array | Ordered {ulid, title, type, memory_type, snippet, score, attested_by, attestation_type, promoted_at, superseded_by?} |
count |
int | Length of hits. |
queried_at |
RFC3339 UTC | When the recall ran. |
manifest_hash |
string | SHA-256 of manifest.jsonl consulted (drift detection between calls). |
dropped |
int | Hits removed by verification (verified_only=true). Surfaced, never silent. |
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.
- 5d ago First seen · 117 lines · 43 tokens per session scan A 0503d9237736
memory-recall is a skill published in the GitHub repository OpenCoven/coven (46 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,692 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / "pass the baton" / "hand off", or a long-running operation needs a durable state checkpoint.
cao-memory
Store, recall, and forget durable facts with CAO memory — user preferences, project conventions, decisions, and corrections that should persist across sessions and agents. Use proactively to check memory before asking the user, and to save anything worth remembering. Distinct from any provider-native memory.
cao-learning
Report task outcomes and distill lessons so the team improves across runs — reportoutcome after each unit of work, retrospector handoffs at natural boundaries, and applying injected lessons. Use in workflows that run repeatedly over similar work items. Requires memory.learningenabled; degrade silently when the tools…
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.