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.
npx skills add jenkinsm13/metashape-mcp --skill metashape-api-lookupgit 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/skills/jenkinsm13/metashape-mcp/metashape-api-lookup)<a href="https://agentmods.dev/skills/jenkinsm13/metashape-mcp/metashape-api-lookup"><img src="https://agentmods.dev/badge/skills/jenkinsm13/metashape-mcp/metashape-api-lookup/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.
<a href="https://agentmods.dev/skills/jenkinsm13/metashape-mcp/metashape-api-lookup"><img src="https://agentmods.dev/badge/skills/jenkinsm13/metashape-mcp/metashape-api-lookup.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00764 |
| Opus 5 | $0.00026 | $0.00382 |
| Sonnet 5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
metashape-api-lookup 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metashape API Lookup
When working on metashape-mcp tools, always verify API parameters against the local reference files rather than guessing.
Reference Files
The project contains these Metashape API references:
| File | Contents | When to Use |
|---|---|---|
api_reference.txt |
Full Python API reference (text, searchable) | Primary reference for parameter names, types, defaults |
metashape_python_api_2_3_0.pdf |
Official PDF API docs | Backup if text version is unclear |
metashape-pro_2_3_en.pdf |
Metashape Pro user manual | For understanding workflow context and UI equivalents |
usgs_ofr20211039.pdf |
USGS photogrammetry best practices | For filtering thresholds and workflow order |
Lookup Procedure
When implementing or modifying an MCP tool:
-
Search
api_reference.txtfirst — Use Grep to find the exact method signature:Grep for: "chunk.buildModel" or "buildModel" or "Chunk.buildModel" -
Check parameter types — Metashape uses its own enum types. Verify which enum a parameter expects:
Grep for: "SurfaceType" or "DataSource" or the specific enum class -
Check
utils/enums.py— See if the string-to-enum mapping already exists. If not, add it. -
Verify defaults — The MCP tool defaults should match best-practice defaults, which may differ from Metashape API defaults. Example:
keep_keypoints: Metashape default=False, MCP default=True (required for incremental alignment)blending_mode: Use "natural" for best quality, not necessarily the API default
Common Gotchas
These are verified facts from the API reference — do NOT guess these:
| Topic | Correct Answer |
|---|---|
alignChunks method param |
Plain int (0=tiepoints, 1=markers, 2=cameras), NOT an enum |
RasterFormatTiles |
IS the correct enum for GeoTIFF export — there is no RasterFormatGeoTIFF |
face_count param |
Use Metashape.CustomFaceCount with face_count_custom=0 for unlimited |
cam.meta["key"] |
Bracket access only — MetaData is C++ object, no .get() method |
chunk.tie_points.points |
Can be None — always check before len() |
classifyGroundPoints |
On chunk.point_cloud, NOT on chunk directly |
exportRaster |
Handles both DEM and orthomosaic (use source_data parameter) |
progress callback |
Callable[[float], bool] — return True to continue, raise to cancel |
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.
- 12d ago First seen · 66 lines · 51 tokens per session scan A 92e17d9a3813
metashape-api-lookup is a skill published in the GitHub repository jenkinsm13/metashape-mcp (34 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 764 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.
Other skills, from other repositories
cad-mesh-3dgs
Bridge CAD, Mesh, and 3DGS representations via the SLAT unified encode-decode framework. Covers mesh↔3DGS conversion, surface extraction, CAD reverse engineering, B-rep/parametric reconstruction, NL-driven assembly, TetSphere physics bridge, PBR material generation. Analyzes 40+ methods. Use when: converting mesh…
3dgs-experiment-planner
Design rigorous experiments for 3DGS research papers. Recommends datasets, baselines, metrics, ablation matrices. Targets CVPR/ICCV/ECCV/SIGGRAPH/TVCG. Use when: designing experiments for a 3DGS paper, selecting datasets/baselines/metrics, planning ablation studies, addressing reviewer concerns on experiments…
3dgs-visualizer
A chart-making tool for research on 3D Gaussian Splatting (3DGS), a technique for representing and rendering 3D scenes from images. It creates radar charts, comparison tables, and timelines for comparing research methods.
nerf-to-3dgs-migrator
Migrate NeRF-based methods to 3DGS via the SLAT unified encode-decode framework. Analyzes component compatibility, provides code templates, identifies issues. Covers encoding, deformation, appearance, geometry. Use when: migrating NeRF method to 3DGS, comparing NeRF vs 3DGS components, designing hybrid NeRF-3DGS…
3dgs-paper-reader
Read and summarize 3DGS research papers. Extracts method architecture, innovations, experimental results from arXiv or local PDFs. Structured output with tables. Knowledge of 819+ methods across 23 categories. Use when: reading or analyzing a 3DGS/NeRF paper, extracting method details from arXiv PDF, summarizing 3D…
cg-paper-writing
Academic paper writing for 3D vision, computer graphics, CAD, and 3D understanding. Covers NeRF, 3DGS, SLAM, point cloud, 3D shape, CAD modeling. Supports CVPR/ICCV/ECCV/SIGGRAPH venues. Multi-agent adversarial review, citation integrity gates, style calibration. Use when: writing or revising a CG/3D vision paper…