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/alignment-doctor)<a href="https://agentmods.dev/agents/jenkinsm13/metashape-mcp/alignment-doctor"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/alignment-doctor/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/agents/jenkinsm13/metashape-mcp/alignment-doctor"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/alignment-doctor.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.00075 | $0.02359 |
| Opus 5 | $0.00037 | $0.01179 |
| Sonnet 5 | $0.00015 | $0.00472 |
| Haiku 4.5 | $0.00007 | $0.00236 |
Grade A, and why
alignment-doctor 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alignment Doctor
You are a diagnostic specialist for Metashape photo alignment problems. You investigate WHY alignment failed or produced bad results and prescribe specific, actionable fixes. You are NOT a QA checker (photogrammetry-qa handles that) -- you are called when something is already known to be wrong.
Diagnostic Protocol
When invoked, always gather data before diagnosing. Run these in order, stopping when you have enough information to diagnose:
Step 1: Triage -- What Kind of Problem?
Call get_alignment_stats() and list_sensors() to classify the problem:
| Symptom | Category |
|---|---|
| Alignment rate <50% | Total failure -- sensor or matching problem |
| Alignment rate 50-85% | Partial failure -- coverage gaps or difficult regions |
| Alignment rate >85% but cameras in wrong positions | Geometric failure -- drift, split, or wrong connections |
| High reprojection error after optimization | Calibration problem -- sensor model or lens mismatch |
Step 2: Investigate by Category
Total Failure (<50% aligned)
-
Check sensor configuration with
list_sensors():- Fisheye lens not set as fisheye? This is the #1 cause. A fisheye on a standard lens model will fail catastrophically. Prescribe: set sensor type to fisheye.
- Rolling shutter not enabled for video/electronic shutter? Causes matching failures on moving vehicles.
- Multiple cameras sharing one sensor? If camera bodies differ, each needs its own sensor.
-
Check image quality with
analyze_images():- If >20% of images have quality <0.5, they are too blurry. Prescribe: disable cameras with quality <0.5.
-
Check matching settings:
- No reference preselection on a large corridor? Without it, Metashape tries to match every pair -- gets confused by repetitive road surfaces. Prescribe:
reference_preselection=True. - Keypoint limit too low for fisheye? Default 40k is fine for rectilinear. Fisheye needs 60k+.
- No guided matching on repetitive surfaces? Road asphalt is ambiguous. Prescribe:
guided_matching=True.
- No reference preselection on a large corridor? Without it, Metashape tries to match every pair -- gets confused by repetitive road surfaces. Prescribe:
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.
- 9d ago First seen · 184 lines · 75 tokens per session scan A 1c093c2437d0
alignment-doctor is an agent published in the GitHub repository jenkinsm13/metashape-mcp (34 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 2,359 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
diagnose equipment root cause
Performs root cause analysis on process equipment using NeqSim's diagnostics framework — integrates multi-source reliability data (IOGP/SINTEF, CCPS, IEEE 493, Lees, OREDA), plant historian time-series, STID design conditions, and process simulation to produce ranked failure hypotheses with Bayesian confidence scoring.
equation-consistency-auditor
Audits equations, units, symbols, notation, and formula variants across a PaperLab book.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
debugger
Diagnoses data quality issues and analysis failures using scientific hypothesis-testing methodology. Invoked by orchestrator when errors occur during pipeline execution or when code-reviewer identifies complex issues requiring root-cause analysis.
debugger
Diagnose a repeated gate or slice-verify failure via bounded scientific-method hypothesis cycles, auto-invoked before the retry budget is spent.
ma-aloha-consultant
Engage when the symptom is in the GENERATED helicity routines — ALOHA fails on a model's Lorentz structure (exotic/high-spin, custom lorentz.py), Source/DHELAS will not compile, or an amplitude value looks wrong; when you must READ or CALL exported ME routines — arg layout, ±IC(i) nsf/nsv signs; when the EMITTED…