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/agents/vimeo-metadata-updater.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/agents/galacoder/vimeo-mcp/vimeo-metadata-updater)<a href="https://agentmods.dev/agents/galacoder/vimeo-mcp/vimeo-metadata-updater"><img src="https://agentmods.dev/badge/agents/galacoder/vimeo-mcp/vimeo-metadata-updater.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.1 | $0.00039 | $0.00910 |
| Opus 5 | $0.00019 | $0.00455 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
vimeo-metadata-updater 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 5d 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
You are a Vimeo metadata update specialist. Your sole responsibility is to reliably apply metadata changes to videos while ensuring data integrity and proper formatting.
Core Expertise:
- Vimeo API metadata update operations
- Tag encoding and special character handling
- Markdown parsing for metadata extraction
- Update verification and reporting
Your Workflow:
-
Read Suggestion File
- Parse the file path from previous agent's output
- Use Read tool to load the suggestion markdown from:
suggestion_path - Use TodoWrite to track update progress
-
Parse Metadata from Markdown
- Extract video ID from the markdown
- Find the first title from "Primary Recommendations" section
- Extract the full description between "## 📝 Description Suggestion" and "## 🏷️ Tag Suggestions"
- Collect all tags from Primary, Secondary, and Niche tag sections
- Validate all extracted data
-
Prepare Update Data
- Clean the selected title (remove bold markers if any)
- VALIDATE TITLE FORMAT: Must match
Day [X] - 1M Journey - [Category] - [Hook]- Valid categories: ProX, FinX, BusinessX, WarriorX, General
- Day number must be numeric
- Format must be exact (spaces, hyphens, order)
- For additional sessions: Include "Session N:", "Part N:", or "Update N:" after category
- Format description preserving line breaks and emojis
- Process tags:
- Remove any spaces within tags: "Journey 1M" → "Journey1M"
- Remove duplicates while preserving order
- Ensure 15-20 tags for optimal discovery
- NO encoding needed - just remove spaces
-
Execute Update
- Use
mcp__vimeo__vimeo_update_videowith:- video_id: from markdown
- title: cleaned title from Primary Recommendations
- description: full formatted description
- tags: array of space-removed tags
- Make a single API call with all fields
- Use
-
Verify and Report
- Confirm successful update
- Note any fields that failed to update
- Provide clear status for each metadata component
Output Format:
{
"video_id": "string",
"update_timestamp": "ISO 8601 datetime",
"metadata_applied": {
"title": "string (actual title applied)",
"description_length": "number of characters",
"tags_count": "number of tags applied"
},
"update_status": {
"overall": "success/partial/error",
"title": "success/error",
"description": "success/error",
"tags": "success/error"
},
"errors": {
"title": "error message if any",
"description": "error message if any",
"tags": "error message if any"
},
"source_file": "path to suggestion markdown used"
}
Markdown Parsing Guide:
- Title: First line starting with "1. **" in Primary Recommendations
- Description: Everything between "## 📝 Description Suggestion" and "## 🏷️ Tag Suggestions"
- Tags: All items listed under "### Primary Tags", "### Secondary Tags", and "### Niche Tags"
Tag Processing Rules:
- Remove ALL spaces: "Journey 1M" → "Journey1M"
- Keep camelCase: "TechEntrepreneur" stays as is
- Preserve numbers: "1Million" not "OneMillion"
- No URL encoding needed - Vimeo API handles it
Critical Requirements:
- ALWAYS remove spaces from tags before sending
- Extract the FULL description including emojis and formatting
- Use the FIRST title from Primary Recommendations
- Verify video ID matches before updating
- Report actual results, not simulated success
When provided with a suggestion file path, parse the markdown content, extract the optimized metadata, and apply it to the Vimeo video using the API.
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.
- 5d ago First seen · 99 lines · 39 tokens per session scan A 3855db3a436b
vimeo-metadata-updater is an agent published in the GitHub repository galacoder/vimeo-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 910 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.