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.
git clone --depth 1 https://github.com/vybe/project_corneliusWrote 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/commands/vybe/project_cornelius/recall)<a href="https://agentmods.dev/commands/vybe/project_cornelius/recall"><img src="https://agentmods.dev/badge/commands/vybe/project_cornelius/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/commands/vybe/project_cornelius/recall"><img src="https://agentmods.dev/badge/commands/vybe/project_cornelius/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.00018 | $0.00450 |
| Opus 5.5 | $0.00007 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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.
This is a copy
100% identical to recall — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Semantic Knowledge Retrieval
You are tasked with retrieving relevant knowledge from the Obsidian vault using multi-layer semantic search.
Search Query
$ARGUMENTS
Instructions
-
First Layer - Initial Search:
- Use
mcp__smart-connections__search_noteswith the query above - Retrieve top 5 most relevant notes (threshold: 0.5)
- Use
Readtool to read the full content of the top 2 results
- Use
-
Second Layer - Direct Associations:
- For the top result from layer 1, use
mcp__smart-connections__get_similar_notes - Retrieve 5 semantically similar notes (threshold: 0.6)
- Use
Readtool to read the full content of the top 2 similar notes
- For the top result from layer 1, use
-
Third Layer - Extended Network:
- Build a connection graph using
mcp__smart-connections__get_connection_graph - Parameters: depth=3, max_per_level=5, threshold=0.65
- This reveals deeper conceptual connections
- Build a connection graph using
Output Format
Present the findings in this structured format:
# Knowledge Recall: [Query Topic]
## Layer 1: Direct Matches
[List notes found with similarity scores and key excerpts]
## Layer 2: First-Degree Associations
[List similar notes with their connections and excerpts]
## Layer 3: Extended Network
[Show the connection graph with relationship strengths]
## Key Insights
[Synthesize the main themes and connections discovered]
## Relevant Content
[Include the most pertinent excerpts from the retrieved notes]
Important Notes
- Focus on quality over quantity
- Highlight unexpected connections
- Provide enough context for the user to understand the relevance
- If search returns no results, try broader terms or related concepts
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 First seen · 59 lines · 18 tokens per session scan A f9cfdd08ef2b
recall is a command published in the GitHub repository vybe/project_cornelius (5 stars, last pushed 11mo ago), licensed MIT. It adds 18 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to recall, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.