project-planner

project-planner is an agent for Claude Code from jenkinsm13/metashape-mcp. It costs 74 tokens per session (2,724 once invoked), scanned A, original, MIT.

A project-status assistant for Metashape and Blender, two tools commonly used to create 3D models from photographs and prepare them for 3D work. It checks what is loaded, what processing stages are complete, and what should happen next.

In plain words
What is it for?
Use it at the start of a work session or when a photogrammetry project is unclear. It checks alignment, point clouds, models, ground-control markers, processing status, Blender objects, and surface-classification clues.
Why use it?
It removes the need to inspect both applications separately when you are unsure how far a project has progressed. It also handles cases where one application has no open project or file.

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 at the start of a work session or when a photogrammetry project is unclear. It checks alignment, point clouds, models, ground-control markers, processing status, Blender objects, and surface-classification clues.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jenkinsm13/metashape-mcp/project-planner
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 project-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/project-planner.svg)](https://agentmods.dev/agents/jenkinsm13/metashape-mcp/project-planner)
Your own site
<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>
Per session 74 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,724 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.00074 $0.02724
Opus 5 $0.00037 $0.01362
Sonnet 5 $0.00015 $0.00545
Haiku 4.5 $0.00007 $0.00272

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

Security

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.

agents/project-planner.md · 250 lines

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):

  1. list_chunks() -- gets chunk list with high-level processing flags
  2. For the active chunk:
    • get_alignment_stats() if has_tie_points is True
    • get_point_cloud_stats() if has_point_cloud is True
    • get_model_stats() if has_model is True
    • list_markers() to check GCP status
  3. get_processing_status() -- is something currently running?

Step 2: Check Blender State

  1. get_scene_info() -- object count, names, types
  2. Count tile objects (names starting with Tile_)
  3. 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

Read the full file on GitHub · 250 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. 8d ago First seen · 250 lines · 74 tokens per session scan A 0645393e8cd2

Subscribe to this mod's changes

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.

Related

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

pedrohcgs/claude-code-my-workflow · 64 tokens

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.

SHAdd0WTAka/Zen-Ai-Pentest · 45 tokens

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.

equinor/neqsim · 61 tokens

mathodology-problem-analyst

Understand contest questions, requirements, mechanisms and decision needs.

sweetcornna/mathodology · 20 tokens

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…

K-Dense-AI/scientific-agents · 78 tokens

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.

GGbond-bo/MemOmics-Agent · 38 tokens