point-cloud-lidar

point-cloud-lidar is a skill for Claude Code, Codex from muend/geoai-skills. It costs 162 tokens per session (2,183 once invoked), scanned A, original, MIT.

A guide to turning LiDAR and other 3D point clouds into usable maps and measurements. LiDAR is distance data collected with laser scans, often stored in LAS, LAZ, or COPC files.

In plain words
What is it for?
Use it to inspect and process point clouds, classify ground points, create bare-earth or surface elevation maps, measure vegetation and buildings, and work with photogrammetry data.
Why use it?
It helps catch problems with coordinate systems, height references, point density, and incorrect point classifications before they distort the results.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the geoai plugin — 18 skills shipped together

Good fit Use it to inspect and process point clouds, classify ground points, create bare-earth or surface elevation maps, measure vegetation and buildings, and work with photogrammetry data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muend/geoai-skills/point-cloud-lidar
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.

Any agent
npx skills add muend/geoai-skills --skill point-cloud-lidar
Clone the repo
git clone --depth 1 https://github.com/muend/geoai-skills

Made for: Claude Code, Codex.

Or install geoai, the plugin that ships this one along with the rest of its 18 skills.

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 point-cloud-lidar

README.md
[![agentmods](https://agentmods.dev/badge/skills/muend/geoai-skills/point-cloud-lidar/github.svg)](https://agentmods.dev/skills/muend/geoai-skills/point-cloud-lidar)
Your own site
<a href="https://agentmods.dev/skills/muend/geoai-skills/point-cloud-lidar"><img src="https://agentmods.dev/badge/skills/muend/geoai-skills/point-cloud-lidar/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.

agentmods 80×15 button for point-cloud-lidar

Your own site · 80×15
<a href="https://agentmods.dev/skills/muend/geoai-skills/point-cloud-lidar"><img src="https://agentmods.dev/badge/skills/muend/geoai-skills/point-cloud-lidar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 162 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,183 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00162 $0.02183
Opus 5 $0.00081 $0.01092
Sonnet 5 $0.00032 $0.00437
Haiku 4.5 $0.00016 $0.00218

Measured 11d ago against content hash 312980ba13d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

point-cloud-lidar 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 11d 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.

skills/point-cloud-lidar/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Point Clouds & LiDAR

Purpose: from raw returns to defensible elevation and structure products. The recurring failure modes: trusting vendor classification blindly, mixing return types in surfaces (DSM from last returns, DTM with vegetation), and ignoring point density when choosing output resolution.

First contact with any cloud

pdal info input.laz --summary        # counts, bounds, CRS, classes, returns

Report before touching anything: point count, density (pts/m² — decides achievable raster resolution), CRS (horizontal AND vertical datum — ellipsoidal vs orthometric heights differ by the geoid undulation, tens of meters in places), classification present?, return numbers present?, flight-line overlap artifacts. A cloud without CRS metadata: resolve from the provider, never assume.

Format and scale

Format Use
LAZ Compressed interchange/archive — default
COPC (cloud-optimized LAZ) Streaming/HTTP range access, web viewers
LAS Only when a tool can't read LAZ
Entwine/EPT Massive multi-tile collections, indexed

Tile large collections; process per-tile with buffered edges (~2× search radius) to avoid seam artifacts in filters and surfaces; drop the buffer on write.

PDAL pipeline pattern

{
  "pipeline": [
    "input.laz",
    {"type": "filters.reprojection", "out_srs": "EPSG:32636"},
    {"type": "filters.outlier", "method": "statistical",
     "mean_k": 8, "multiplier": 2.5},
    {"type": "filters.smrf", "slope": 0.15, "window": 18.0,
     "threshold": 0.5, "scalar": 1.2},
    {"type": "writers.las", "filename": "classified.laz",
     "extra_dims": "all"}
  ]
}

Run: pdal pipeline pipeline.json. Denoise BEFORE ground classification (low outliers below ground destroy SMRF/CSF); tune slope up for steep terrain, window to the largest non-ground object (big buildings need bigger windows).

Ground classification & DTM

  • If vendor class 2 (ground) exists: audit it on 2-3 cross-sections (bridges, dense canopy, steep slopes) before trusting; reclassify where it fails.
  • Algorithms: SMRF (PDAL default, robust), CSF (cloth simulation, good in steep forest). Parameters are terrain-dependent — show a cross-section plot as evidence, not just the parameter list.
  • DTM from ground-only points; interpolation: TIN → raster (standard for DTM) or IDW for dense clouds. Output resolution ≥ ~1/√density; a 0.5 m DTM from 1 pt/m² data is invented detail.
  • DSM from first returns / highest-point binning. CHM = DSM − DTM, clamp negatives to 0, and use a pit-free algorithm for forestry (naive CHMs are pocked by within-crown pits).

Read the full file on GitHub · 181 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 181 lines · 162 tokens per session scan A 312980ba13d9

Subscribe to this mod's changes

point-cloud-lidar is a skill published in the GitHub repository muend/geoai-skills (17 stars, last pushed 7d ago), licensed MIT. It adds 162 tokens to every session and 2,183 once invoked, about $0.0008 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-31.