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/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/process-video)<a href="https://agentmods.dev/commands/lttr/claude-marketplace/process-video"><img src="https://agentmods.dev/badge/commands/lttr/claude-marketplace/process-video/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/lttr/claude-marketplace/process-video"><img src="https://agentmods.dev/badge/commands/lttr/claude-marketplace/process-video.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.00007 | $0.00253 |
| Opus 5 | $0.00003 | $0.00127 |
| Sonnet 5 | $0.00001 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
process-video 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 9d 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
Video to Article Conversion
Convert a lecture or presentation video into multiple text formats.
Usage
/process-video https://youtube.com/watch?v=...- Process YouTube video/process-video /path/to/folder- Process video in existing folder/process-video- Interactive mode (will ask for input)
Load video-to-article skill first.
Execute the video-to-article workflow for: {arg1}
Handling file references:
- When user provides path via @ syntax (e.g., @"folder name"), extract the actual path
- The @ syntax provides file/folder context automatically - use the referenced path
- If path contains spaces and quotes, clean them:
@"My Folder"→My Folder - Support both absolute and relative paths
- Navigate to the folder before executing workflow
Input types:
- YouTube URL: Detect youtube.com or youtu.be pattern and download first
- Folder path: Navigate to folder and process existing video
- Empty/Interactive: Ask user for input or use current directory
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.
- 9d ago First seen · 35 lines · 7 tokens per session scan A 51a1f997b3fc
process-video is a command published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 253 once invoked, about $0.0000 per session on Opus 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 commands, from other repositories
explain
Provide clear explanations of code, concepts, and system behavior with educational clarity.
help-flow
Help about Rosetta: explains capabilities and usage.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.
doc-explain
Command "doc-explain" from christopherlouet/claude-base, covering explain agent, code to explain, objective, workflow and expected output.
explain
Explain a concept, code pattern, or topic — the minimum that makes it understood, with a diagram only when it shows a mechanism.
how-to-research
Learn which MCP tools to use for researching a topic.