Borrowing it
Nothing to install: this file belongs to galacoder/vimeo-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/galacoder/vimeo-mcp/main/.claude/commands/vimeo-titles.mdgit clone --depth 1 https://github.com/galacoder/vimeo-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/galacoder/vimeo-mcp/vimeo-titles)<a href="https://agentmods.dev/commands/galacoder/vimeo-mcp/vimeo-titles"><img src="https://agentmods.dev/badge/commands/galacoder/vimeo-mcp/vimeo-titles/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/galacoder/vimeo-mcp/vimeo-titles"><img src="https://agentmods.dev/badge/commands/galacoder/vimeo-mcp/vimeo-titles.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.00017 | $0.03642 |
| Opus 5.5 | $0.00007 | $0.01457 |
| Sonnet 5.5 | $0.00003 | $0.00728 |
| Haiku 4.5 | $0.00002 | $0.00364 |
Grade A, and why
vimeo-titles 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vimeo Video Title Optimization Orchestrator
Process the following videos: $ARGUMENTS
Context
- Series: Journey to 1M Revenue/Impact
- Known Projects: ProX, FinX, BusinessX, WarriorX, Proco Pro XI
- Optimization Goal: Generate viral titles, descriptions, and tags
- Journey Start: 2024-10-04 = Day 1
🎭 Agent Orchestra Execution
This command orchestrates 6 specialized agents in a coordinated pipeline with explicit Task tool invocations and MCP access.
🚀 Phase 1: Setup and Data Collection
I'll start by parsing the arguments and setting up the workflow:
Parsing target date from: $ARGUMENTS
Let me parse the date argument and create the export directory structure for this workflow.
Converting the date argument to standardized format...
Setting up export directory:
Creating /tmp/vimeo-optimization-{timestamp}/ with subdirectories for data flow between agents.
Now I'll deploy the first agent to collect video data using direct MCP tools:
I'll deploy the vimeo-data-collector agent to find videos for the target date and download AI captions:
Task( subagent_type: "vimeo-data-collector", description: "Collect videos and download AI captions for target date", prompt: `CRITICAL: You MUST use real MCP tools. Do NOT simulate data.
TARGET: Process videos for date parsed from "$ARGUMENTS"
REQUIRED MCP WORKFLOW:
-
Use mcp__vimeo__vimeo_list_videos_from_folder_by_date( folder_id="22346328", # "Document to 1M success" folder (490 videos) target_date="{PARSED_DATE}", # Convert $ARGUMENTS to YYYY-MM-DD format user_id="me" )
-
For EACH video found in the target date range:
- Use mcp__vimeo__vimeo_get_video_details(video_id) to get full metadata
- Use mcp__vimeo__vimeo_download_ai_captions(video_id, language="en-x-autogen") FIRST (priority)
- If AI captions fail, fallback to mcp__vimeo__vimeo_download_transcript(video_id)
- Track transcript_source: "AI-generated" or "manual" for each video
-
Create comprehensive collection data and export to: /tmp/vimeo-optimization-{timestamp}/collection/videos.json
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.
- 2mo ago First seen · 476 lines · 17 tokens per session scan A 4d04845a05b2
vimeo-titles is a command published in the GitHub repository galacoder/vimeo-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 3,642 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.
vimeo-titles compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| vimeo-titlesgalacoder/vimeo-mcp | Command | 0 | 3mo ago | MIT | A | 17 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |