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 commands/bundl-ai/bundl-cli/recallgit clone --depth 1 https://github.com/Bundl-AI/bundl-cliWrote 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/bundl-ai/bundl-cli/recall)<a href="https://agentmods.dev/commands/bundl-ai/bundl-cli/recall"><img src="https://agentmods.dev/badge/commands/bundl-ai/bundl-cli/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.00000 | $0.00297 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 4d 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
Path rules — read first
- Company files: workspace/company/[name].md NEVER workspace/[name].md (wrong) ALWAYS workspace/company/[name].md (correct)
- Memory files: workspace/memory/[name].md
- Artifact files: workspace/artifacts/[type]/[name].md
- Commands files: workspace/commands/[name].md
- Use >> to append when the file already has real content. If the file still only has the stub "# Title" and "Not yet defined.", use > to overwrite with the title, a blank line, and your content (do not leave the stub). Exception: /save always uses > for new artifact files.
- Maximum 2 tool calls for /note: call 1 cat target file, call 2 echo >> append (or echo > if file is still stub-only). Do not mkdir, do not check if file exists. Files are guaranteed to exist.
/recall [topic]
What it does
Greps all workspace files for the topic. Returns a clean summary.
Exact steps
- grep -ri "[topic]" workspace/company/
- grep -ri "[topic]" workspace/memory/longterm.md
- grep -ri "[topic]" workspace/artifacts/ Compile results into clean summary.
If nothing found
"Nothing on [topic] yet. Tell me about it and use /note to save it."
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.
- 4d ago First seen · 24 lines · 0 tokens per session scan A 83e02ef4abed
recall is a command published in the GitHub repository Bundl-AI/bundl-cli (7 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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 commands, from other repositories
index
Index (or re-index) the current project into the OpenTrace knowledge graph. Use when: "index this repo", "re-index", "update the graph", "build the index".
sync-ai-memory
Synchronize AI-critical repository documents without modifying Engram memory.
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.
cleanup
Delete promoted content from the .memory/ directory.
memory-bank
Update memory bank. If not exist initialize memory bank.