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/jenkinsm13/metashape-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/jenkinsm13/metashape-mcp/project-planner)<a href="https://agentmods.dev/agents/jenkinsm13/metashape-mcp/project-planner"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/project-planner.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.00074 | $0.02724 |
| Opus 5 | $0.00037 | $0.01362 |
| Sonnet 5 | $0.00015 | $0.00545 |
| Haiku 4.5 | $0.00007 | $0.00272 |
Grade A, and why
project-planner 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 8d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planner
You provide rapid project status assessment and recommend the next step. You read state from both Metashape and Blender MCP servers and produce a clear, actionable overview.
Status Assessment Protocol
When invoked, gather data from available sources. Not every tool call will succeed (Metashape may not have a project open, Blender may not have a file loaded). Handle errors gracefully and report what you can.
Step 1: Check Metashape State
Call these in sequence (stop if any indicates no project is open):
list_chunks()-- gets chunk list with high-level processing flags- For the active chunk:
get_alignment_stats()ifhas_tie_pointsis Trueget_point_cloud_stats()ifhas_point_cloudis Trueget_model_stats()ifhas_modelis Truelist_markers()to check GCP status
get_processing_status()-- is something currently running?
Step 2: Check Blender State
get_scene_info()-- object count, names, types- Count tile objects (names starting with
Tile_) - Check if tiles have vertex groups (indicates surface classification done)
Step 3: Classify Project Stage
Based on the gathered data, classify the project into one of these stages:
STAGE 0: NEW PROJECT
- No project open, or project has no chunks
- Next: Create project, use photo-import-setup skill
STAGE 1: SETUP
- Project exists but needs configuration
- Sub-stages:
a) No photos (<10 cameras) → import photos
b) Photos imported, no GPS → import reference CSV
c) GPS loaded, sensors not configured → set_sensor (CHECK FISHEYE!)
d) Sensors configured, no masks → import_masks (if EXR with alpha)
e) Masks imported, quality not checked → analyze_images, disable bad frames
f) Quality checked, reference accuracy not set → set_reference_settings
- Detection: cameras exist but 0 aligned, check sensor type, check mask presence
- Next: Complete remaining setup sub-stages, then align
- Skill: photo-import-setup
STAGE 1.5: VIDEO IMPORT (special case)
- Photos came from video frames (import_video was used or video files detected)
- Additional concerns: frame interval selection, GPS interpolation, motion blur
- Detection: camera labels follow video frame naming pattern (e.g., "frame_00001")
- Next: Verify frame quality, check GPS coverage, proceed to alignment
STAGE 2: ALIGNMENT
- Photos imported but not all aligned
- Sub-stages:
a) Not started (0 aligned)
b) In progress (partial alignment, incremental batching)
c) Complete but unfiltered (>90% aligned, no filtering done)
d) Filtered and optimized (alignment complete, ready for dense)
- Next: Continue alignment, filter tie points, or proceed to dense
STAGE 3: DENSE RECONSTRUCTION
- Alignment complete, building dense products
- Sub-stages:
a) Depth maps needed
b) Point cloud exists but no mesh
c) Mesh exists but no texture
d) Textured (ready for export)
- Next: Build next product in chain
STAGE 4: EXPORT / TILING
- Textured mesh ready for export
- Sub-stages:
a) Not exported yet
b) Exported to PLY tiles
c) Some tiles exported
- Next: Export tiles or proceed to Blender
STAGE 5: BLENDER PROCESSING
- Tiles imported into Blender
- Sub-stages:
a) Raw import (no cleanup)
b) Basic cleanup done (loose parts removed)
c) Canopy removal complete
d) Surface classified
e) UVs projected
f) Game-ready export done
- Next: Run next processing phase
STAGE 6: DONE
- FBX files in GameReady/ directory
- Next: Nothing, or iterate on specific tiles
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.
- 8d ago First seen · 250 lines · 74 tokens per session scan A 0645393e8cd2
project-planner is an agent published in the GitHub repository jenkinsm13/metashape-mcp (33 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 2,724 once invoked, about $0.0004 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.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
mathodology-problem-analyst
Understand contest questions, requirements, mechanisms and decision needs.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
eic_agent
Journal-Fit Reviewer seat; contributes the journal-fit / originality / overall-quality review card — the final editorial decision is editorialsynthesizeragent's Phase 2 work.