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 muend/geoai-skills --skill point-cloud-lidargit clone --depth 1 https://github.com/muend/geoai-skillsWrote 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/muend/geoai-skills/point-cloud-lidar)<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.
<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>- NVIDIA SkillSpector pass
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.00162 | $0.02183 |
| Opus 5 | $0.00081 | $0.01092 |
| Sonnet 5 | $0.00032 | $0.00437 |
| Haiku 4.5 | $0.00016 | $0.00218 |
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.
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).
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.
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.
- 11d ago First seen · 181 lines · 162 tokens per session scan A 312980ba13d9
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.
Other skills, from other repositories
detect-objects
Run pre-trained AI models on geospatial imagery. Detect buildings, cars, ships, solar panels, agriculture fields, or use text-prompted segmentation with GroundedSAM. Requires GPU for best performance.
process-raster
Process raster data: clip by bounding box, stack multiple bands, mosaic GeoTIFFs, or convert between raster and vector formats.
download-data
Download NAIP aerial imagery for a bounding box. Specify coordinates as minx,miny,maxx,maxy in WGS84 and optionally a year.
inspect-geo
Inspect any raster or vector geospatial file. Returns CRS, bounds, bands, resolution, dtype, attribute summaries, and band statistics. Supports GeoTIFF, Shapefile, GeoJSON, GeoPackage, GeoParquet, and more.
search-stac
Search and download satellite imagery from Microsoft Planetary Computer. Browse available collections, search by bbox and time range, list assets, and download specific items.
gdal
Use when processing geospatial raster/vector data via command line — format conversion (Shapefile to GeoJSON), reprojection, DEM analysis, NDVI calculation, mosaicking. GDAL/OGR CLI: the industry standard for batch geospatial data processing with 50+ command-line tools (ogr2ogr, gdalwarp, gdaltranslate, gdalcalc).