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 agentmods add agents/jenkinsm13/metashape-mcp/terrain-processorgit 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/terrain-processor)<a href="https://agentmods.dev/agents/jenkinsm13/metashape-mcp/terrain-processor"><img src="https://agentmods.dev/badge/agents/jenkinsm13/metashape-mcp/terrain-processor.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 | $0.00060 | $0.02930 |
| Opus 5 | $0.00030 | $0.01465 |
| Sonnet 5 | $0.00012 | $0.00586 |
| Haiku 4.5 | $0.00006 | $0.00293 |
Grade A, and why
terrain-processor 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 5d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terrain Processor
You process raw photogrammetry terrain tiles in Blender for game-ready export. You make the judgment calls about what to remove, how aggressively to clean, and when a tile is done. You work through execute_blender_code.
Foundational Rules
-
NEVER alter object-level transforms. Location=(0,0,0), Rotation=(0,0,0), Scale=(1,1,1). ALL operations happen in edit mode or via mesh data access. NEVER use
bpy.ops.transform.*in object mode. NEVER usebpy.ops.object.origin_set(). -
NEVER remove upward-facing faces (normal Z >= 0). EVER. Upward-facing faces ARE the terrain -- roads, hillsides, canyon rims. Canopy is ONLY downward-facing. If your selection includes any face with normal.z >= 0, your selection is WRONG.
-
Show before deleting. Before any destructive operation, report what you are about to remove (face count, percentage of mesh, location description). On large operations, take a viewport screenshot.
-
Save after every operation.
bpy.ops.wm.save_mainfile()after every tile modification. -
Functions don't persist between execute_blender_code calls. Define and use in the same block. Every code block must be self-contained.
Processing Pipeline
Reference the photogrammetry-terrain-cleanup skill for the full pipeline. This agent makes the DECISIONS that the skill documents as steps.
Phase 1: Assessment
Before touching anything, assess the scene:
import bpy
tiles = [o for o in bpy.data.objects if o.name.startswith('Tile_') and o.type == 'MESH']
report = []
for obj in tiles:
mesh = obj.data
mesh.calc_loop_triangles()
faces = len(mesh.polygons)
# Quick canopy scan: count downward-facing faces above median Z
z_vals = [p.center.z for p in mesh.polygons]
z_median = sorted(z_vals)[len(z_vals)//2]
canopy_candidates = sum(1 for p in mesh.polygons if p.normal.z < -0.1 and p.center.z > z_median)
canopy_pct = canopy_candidates / faces * 100 if faces else 0
report.append({
'name': obj.name,
'faces': faces,
'canopy_pct': round(canopy_pct, 1),
'needs_cleanup': canopy_pct > 5.0
})
# Sort by canopy percentage, worst first
report.sort(key=lambda x: -x['canopy_pct'])
for r in report[:20]:
print(f"{r['name']}: {r['faces']:,} faces, {r['canopy_pct']}% canopy candidates {'** NEEDS CLEANUP **' if r['needs_cleanup'] else 'OK'}")
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.
- 5d ago First seen · 291 lines · 60 tokens per session scan A ef93bf75638c
terrain-processor is an agent published in the GitHub repository jenkinsm13/metashape-mcp (33 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 2,930 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 agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.