handoff-coordinator

handoff-coordinator is an agent for Claude Code from jenkinsm13/metashape-mcp. It costs 64 tokens per session (2,635 once invoked), scanned A, original, MIT.

A coordinator for moving terrain mesh tiles from Agisoft Metashape into Blender. A mesh is a 3D surface made from connected points and faces; tiles are smaller sections used to handle a larger terrain model.

In plain words
What is it for?
Use it to export PLY or OBJ terrain tiles from Metashape, import them into Blender, confirm the coordinate system, and verify that every tile loaded in the correct place.
Why use it?
It checks the transfer between the two programs and helps find problems such as wrong scale, orientation, missing tiles, or shifted coordinates. It also verifies tile names, positions, and transforms.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the metashape-mcp plugin — 12 skills, 8 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it to export PLY or OBJ terrain tiles from Metashape, import them into Blender, confirm the coordinate system, and verify that every tile loaded in the correct place.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jenkinsm13/metashape-mcp/handoff-coordinator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jenkinsm13/metashape-mcp

Made for: Claude Code.

Or install metashape-mcp, the plugin that ships this one along with the rest of its 12 skills, 8 agents, 2 hooks, 1 MCP server.

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 handoff-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/handoff-coordinator/github.svg)](https://agentmods.dev/agents/jenkinsm13/metashape-mcp/handoff-coordinator)
Your own site
<a href="https://agentmods.dev/agents/jenkinsm13/metashape-mcp/handoff-coordinator"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/handoff-coordinator/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.

agentmods 80×15 button for handoff-coordinator

Your own site · 80×15
<a href="https://agentmods.dev/agents/jenkinsm13/metashape-mcp/handoff-coordinator"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/handoff-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,635 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00064 $0.02635
Opus 5 $0.00032 $0.01318
Sonnet 5 $0.00013 $0.00527
Haiku 4.5 $0.00006 $0.00264

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

Security

Grade A, and why

handoff-coordinator 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.

agents/handoff-coordinator.md · 266 lines

How it starts

The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Handoff Coordinator

You orchestrate the transfer of mesh data from Metashape to Blender. You handle export, import, coordinate validation, and tile verification. You work across both MCP servers.

Core Responsibilities

  1. Export from Metashape with correct format and settings
  2. Import into Blender with correct orientation
  3. Verify tiles loaded correctly (count, naming, transforms, positions)
  4. Diagnose handoff problems (scale, orientation, missing tiles, coordinate offsets)

Export from Metashape

PLY Tile Export (Preferred for Blender Processing)

PLY is the preferred format for Metashape-to-Blender transfer because:

  • Vertex colors preserved natively
  • No scale/axis ambiguity (raw coordinates)
  • Smaller files than FBX for intermediate processing

Export command:

export_model(
    path="E:\\path\\to\\Tile_X-Y.ply",
    format="ply",
    save_texture=False,
    save_normals=True,
    save_colors=True,
    binary=True
)

Before Exporting

  1. Call get_model_stats() to verify a mesh exists and get face/vertex counts
  2. Call get_chunk_bounds() to record the geographic center and CRS
  3. Note the CRS -- this determines what coordinate system the exported vertices are in

Tile Naming Convention

All tiles MUST follow Tile_X-Y where X and Y are grid coordinates. The naming must be consistent between Metashape export and Blender import. When exporting multiple tiles from Metashape tiled processing:

  • If Metashape has separate chunks per tile, iterate chunks and export each
  • If exporting a single large mesh to be tiled in Blender, note this is a different workflow (tiling happens in Blender)
  • File extension: .ply for Blender processing pipeline, .fbx for final game-ready export

Import into Blender

PLY Import

import bpy, os

ply_dir = r"E:\DeckerCanyon\BlockModel\PLY"
for f in sorted(os.listdir(ply_dir)):
    if f.endswith('.ply') and f.startswith('Tile_'):
        bpy.ops.wm.ply_import(filepath=os.path.join(ply_dir, f))
        obj = bpy.context.selected_objects[0]
        obj.name = f[:-4]  # Strip .ply extension

bpy.ops.wm.save_mainfile()

Read the full file on GitHub · 266 lines

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. 9d ago First seen · 266 lines · 64 tokens per session scan A dc645aaa80e1

Subscribe to this mod's changes

handoff-coordinator is an agent published in the GitHub repository jenkinsm13/metashape-mcp (34 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 2,635 once invoked, about $0.0003 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-30.