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 kalinbogatzevski/captain-memo --skill recallgit clone --depth 1 https://github.com/kalinbogatzevski/captain-memoWrote 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/kalinbogatzevski/captain-memo/recall)<a href="https://agentmods.dev/skills/kalinbogatzevski/captain-memo/recall"><img src="https://agentmods.dev/badge/skills/kalinbogatzevski/captain-memo/recall/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/kalinbogatzevski/captain-memo/recall"><img src="https://agentmods.dev/badge/skills/kalinbogatzevski/captain-memo/recall.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00387 |
| Opus 5.5 | $0.00014 | $0.00155 |
| Sonnet 5.5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
recall 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 1mo 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.
What it actually says
Captain Memo — recall full content by doc_id
When the user invokes this skill, they want the full text of a previously-found hit, not just a snippet.
What to do
- Take the user's argument as the doc_id (e.g.
memory:feedback_no_mocked_db:abc1234). - Call the captain-memo MCP tool
get_fullwithdoc_idset to that value. The MCP server sends the worker's secret for you: there is no token to handle. - Format the response. The body is
{ content: "...", metadata: {...} }.
Output format
Show the source path from metadata.source_path first as a header, then the full content, then a small footer with notable metadata (memory_type, created_at_epoch as a date if present, etc.).
📄 ~/.claude/projects/.../memory/feedback_no_mocked_db.md
type: feedback · 2026-04-15
In this project, **do NOT** mock the database in integration tests: they
must run against a real test database.
[…full content…]
On error
- 404 not_found: tell the user "no document with that doc_id — was the search recent? Try
/captain-memo:searchagain to get fresh doc_ids" - 401: the call carried no valid worker secret (a session started before 0.52.0 sends none). Tell the user to restart the AI session;
captain-memo doctorlists the routes still called without one - worker unreachable:
captain-memo doctorto diagnose
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.
- 1mo ago Changed · -10 lines f9194c83304b
- 2mo ago First seen · 45 lines · 36 tokens per session scan A 4dfe78695d21
recall is a skill published in the GitHub repository kalinbogatzevski/captain-memo (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 36 tokens to every session and 387 once invoked, about $0.0001 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-31.
Other skills, from other repositories
memem-mine
Opt in to memem's event-triggered mining. New sessions are mined automatically via the Stop hook.
wenlan-capture
Save a memory to Wenlan in flow, or save something from this conversation as one note when the user asks for a note. Use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as /wenlan-capture .
wenlan-handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /wenlan-handoff.
curate
Power-user audit of Wenlan's pending surfaces: accept or dismiss pending revisions (conflicts/merges), or audit pending captures (not yet confirmed). Most users want /brief for revisions; that handles the daily flow. Use /wenlan curate only for explicit deep-walk audits after bulk imports, or to walk the full queue…
wenlan
A single command entry point for Wenlan, a tool that checks its setup and connection and turns stored memories into notes. It can also open or list notes and report its current status.
wenlan-recall
Search Wenlan's local memory by query. Targeted lookup, not orientation. Invoked as /wenlan-recall . Use when the user asks "do you remember", "what do you know about", "look up".