vimeo-mcp: Agent for Claude Code

.claude/agents/vimeo-metadata-updater.md

vimeo-metadata-updater is an agent for Claude Code from galacoder/vimeo-mcp. It costs 39 tokens per session (910 once invoked), scanned A, original, MIT.

An agent that applies prepared titles, descriptions, and tags to Vimeo videos through the Vimeo API. It reads metadata suggestions from a Markdown file, checks their format, and reports the update.

In plain words
What is it for?
Use it as the final step after metadata suggestions are prepared, to update video titles, descriptions, and tags and verify the result.
Why use it?
It removes the manual work of copying metadata into Vimeo while checking that the selected information is complete and correctly formatted.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

This is galacoder/vimeo-mcp's own configuration. It tells Claude Code how to work on vimeo-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vimeo-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/galacoder/vimeo-mcp/main/.claude/agents/vimeo-metadata-updater.md
Clone the repo
git clone --depth 1 https://github.com/galacoder/vimeo-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for vimeo-metadata-updater

README.md
[![agentmods](https://agentmods.dev/badge/agents/galacoder/vimeo-mcp/vimeo-metadata-updater.svg)](https://agentmods.dev/agents/galacoder/vimeo-mcp/vimeo-metadata-updater)
Your own site
<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>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 910 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 3855db3a436b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.claude/agents/vimeo-metadata-updater.md · 99 lines

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:

  1. 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
  2. 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
  3. 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
  4. Execute Update

    • Use mcp__vimeo__vimeo_update_video with:
      • 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
  5. 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.

Changes

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.

  1. 5d ago First seen · 99 lines · 39 tokens per session scan A 3855db3a436b

Subscribe to this mod's changes

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.