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/Galbaz1/video-research-mcpWrote 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/galbaz1/video-research-mcp/recall)<a href="https://agentmods.dev/commands/galbaz1/video-research-mcp/recall"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/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/galbaz1/video-research-mcp/recall"><img src="https://agentmods.dev/badge/commands/galbaz1/video-research-mcp/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.00011 | $0.02182 |
| Opus 5 | $0.00005 | $0.01091 |
| Sonnet 5 | $0.00002 | $0.00436 |
| Haiku 4.5 | $0.00001 | $0.00218 |
Grade C, and why
recall scanned grade C 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If the user asks to delete a result, confirm first, then note the directory path so they can remove it manually: `rm -rf <path>`. Commands cannot delete memory files. How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recall: $ARGUMENTS
Browse saved results from previous /gr:* commands and search the knowledge store.
Find the Memory Directory
Use Glob on ~/.claude/projects/*/memory/gr/ to find saved results. There may be results across multiple project directories — check all of them.
Check Knowledge Store
Call knowledge_stats() first. If it returns collection counts, Weaviate is available — use semantic search for keyword queries. If it returns an error, use filesystem-only mode.
knowledge_stats() returns immediately when Weaviate is not configured (no network call). No performance impact for non-Weaviate users.
Behavior
If no arguments given ($ARGUMENTS is empty):
-
Call
knowledge_stats()(reuse availability check result) -
Use
Globwith pattern~/.claude/projects/*/memory/gr/**/analysis.mdto find all saved results -
For each result, read the first 5 lines to get the title and check for visualization artifacts:
- Check if
concept-map.html,evidence-net.html, orknowledge-graph.htmlexists alongsideanalysis.md - Check if
screenshot.pngexists
- Check if
-
Present unified overview:
Knowledge Store (if available) X objects across 12 collections ResearchFindings: N | VideoAnalyses: N | ContentAnalyses: N | ...
Project Memory (filesystem) Group by category with visualization indicators:
Research (
gr/research/)topic-slug— 📊 (has evidence network)
Video Notes (
gr/video/)video-slug— 📊 (has concept map)
Video Chats (
gr/video-chat/)chat-slug— 📊 (has concept map)
Analyses (
gr/analysis/)source-slug— 📊 (has knowledge graph)
Legend: 📊 = interactive visualization available
-
Invite user to search, browse by category, filter by knowledge state, or ask a question
If arguments match a category (research, video, video-chat, analysis):
Category-to-collection mapping:
- research → ResearchFindings, ResearchPlans
- video → VideoAnalyses, VideoMetadata
- video-chat → SessionTranscripts
- analysis → ContentAnalyses
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.
- 10d ago First seen · 192 lines · 11 tokens per session scan C e0c2866c3952
recall is a command published in the GitHub repository Galbaz1/video-research-mcp (23 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,182 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
mem-prune
Removes old low-importance memories.
mem-last
Prints latest memory cards for the current project.
mem-search
Searches memory candidates using local FTS.
mem-status
Shows memory database status for the current project id.
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.