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 znlgis/opengis-skills --skill geoserver-rest-apigit clone --depth 1 https://github.com/znlgis/opengis-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/znlgis/opengis-skills/geoserver-rest-api)<a href="https://agentmods.dev/skills/znlgis/opengis-skills/geoserver-rest-api"><img src="https://agentmods.dev/badge/skills/znlgis/opengis-skills/geoserver-rest-api/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/znlgis/opengis-skills/geoserver-rest-api"><img src="https://agentmods.dev/badge/skills/znlgis/opengis-skills/geoserver-rest-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 214 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00108 | $0.04370 |
| Opus 5.5 | $0.00043 | $0.01748 |
| Sonnet 5.5 | $0.00022 | $0.00874 |
| Haiku 4.5 | $0.00011 | $0.00437 |
Grade A, and why
geoserver-rest-api scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: "Use when automating GeoServer 3.0.2 over REST — POST /rest/workspaces, datastores, featuretypes, PUT Shapefile ZIP to file.shp, GeoTIFF to coveragestores, upload SLD as application/vnd.ogc.sld+xml, ?recurse How it starts
The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目地址： https://github.com/geoserver/geoserver
REST API 文档： https://docs.geoserver.org/latest/en/user/rest/index.html
API 参考： https://docs.geoserver.org/stable/en/user/rest/api/index.html
最新版本： GeoServer 3.0.2（2026-10-19，安全修复版；官方下载）
许可证： GPL-2.0
概述
GeoServer 是一个基于 Java 的开源地理空间数据服务器，实现了 OGC WMS、WFS、WCS、WMTS 等标准协议。GeoServer REST API 提供了完整的 RESTful 配置管理接口，可通过标准 HTTP 方法（GET / POST / PUT / DELETE）对 GeoServer 的各类资源进行编程式管理。
REST API 的典型用途包括：
- 自动化部署：批量创建工作空间、数据存储、发布图层
- CI/CD 集成：在持续集成流水线中自动配置 GeoServer
- AI 智能体：通过 HTTP 接口让 AI 自主管理地图服务
- 运维脚本：批量修改样式、更新数据源连接参数
基础 URL 格式： http://{host}:{port}/geoserver/rest
默认认证： 用户名 admin，密码 geoserver（HTTP Basic Auth）
数据格式： 支持 JSON 和 XML，通过 Accept / Content-Type 请求头或 URL 后缀（.json / .xml）指定。
环境准备与认证方式
所有写操作（POST / PUT / DELETE）均需认证。GeoServer 默认使用 HTTP Basic Auth：
# curl 方式
curl -u admin:geoserver ...
# HTTP Header 方式
Authorization: Basic YWRtaW46Z2Vvc2VydmVy
API 端点一览
REST API 按资源分组，完整端点清单见 reference/endpoints.md：
| 资源组 | 基础路径 | 资源组 | 基础路径 |
|---|---|---|---|
| 系统管理 | /rest/about/*、/rest/reload、/rest/reset |
图层 | /rest/layers |
| 工作空间 | /rest/workspaces |
图层组 | /rest/layergroups |
| 命名空间 | /rest/namespaces |
样式 | /rest/styles |
| 数据存储 | /rest/workspaces/{ws}/datastores |
OGC 服务设置 | /rest/services/{wms|wfs|wcs|wmts}/settings |
| 要素类型 | .../datastores/{ds}/featuretypes |
安全 | /rest/security/* |
| 覆盖存储 / 覆盖 | /rest/workspaces/{ws}/coveragestores |
GeoWebCache | /gwc/rest/* |
常用操作示例
1. 获取 GeoServer 版本
curl -u admin:geoserver \
"http://localhost:8080/geoserver/rest/about/version.json"
2. 创建工作空间
curl -u admin:geoserver -XPOST \
-H "Content-Type: application/json" \
-d '{"workspace":{"name":"myws"}}' \
"http://localhost:8080/geoserver/rest/workspaces"
3. 创建 PostGIS 数据存储
What ships with it
1 file 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.
- 5d ago Changed · -10 lines · +55 tokens per session 97dab1007531
- 11d ago Changed · -77 lines 64827e5b1646
- 1mo ago Changed · +1 lines 3f0941ce3c40
- 1mo ago Changed c75198aff46d
- 1mo ago First seen · 469 lines · 53 tokens per session scan A 2ad0bd96e562
geoserver-rest-api is a skill published in the GitHub repository znlgis/opengis-skills (72 stars, last pushed 6d ago), licensed MIT. It adds 108 tokens to every session and 4,370 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
http-client
An HTTP client for sending requests to web services. It supports common request methods, custom headers, authentication, and formatted responses.
ask-curl
AI-assisted cURL requests. Describe what you want in natural language and get a well-formed cURL command. Supports secret injection via 1Password (op://), request history, response parsing, and chained requests.
api-design
Design REST APIs with consistent naming, error handling, versioning, and pagination. Use when designing a new API, reviewing an existing one, or writing an OpenAPI spec.
api-versioning-strategy
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.
api-design
REST API design patterns. URL naming, HTTP status codes, pagination, RFC 7807 error responses, versioning, and OpenAPI.
api-design-rest
When creating or extending an HTTP API for client consumption.