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 CesiumGS/cesiumjs-ai-starter-app --skill czml-clockgit clone --depth 1 https://github.com/CesiumGS/cesiumjs-ai-starter-appWrote 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/cesiumgs/cesiumjs-ai-starter-app/czml-clock)<a href="https://agentmods.dev/skills/cesiumgs/cesiumjs-ai-starter-app/czml-clock"><img src="https://agentmods.dev/badge/skills/cesiumgs/cesiumjs-ai-starter-app/czml-clock/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/cesiumgs/cesiumjs-ai-starter-app/czml-clock"><img src="https://agentmods.dev/badge/skills/cesiumgs/cesiumjs-ai-starter-app/czml-clock.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.00056 | $0.00529 |
| Opus 5.5 | $0.00022 | $0.00212 |
| Sonnet 5.5 | $0.00011 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
czml-clock 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 1mo 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.
What it actually says
CZML Document Clock
- The "document" packet (always the first packet) MAY carry a "clock":
{ "interval": "<ISO8601 start>/<ISO8601 end>", "currentTime": "<ISO8601>", "multiplier": <number>, "range": "LOOP_STOP" | "CLAMPED" | "UNBOUNDED", "step": "SYSTEM_CLOCK_MULTIPLIER" | "SYSTEM_CLOCK" | "TICK_DEPENDENT" }to populate the viewer's timeline for time-dynamic scenes. - Whenever the intent specifies playback behavior (a start/stop time, a time multiplier, or looping), you MUST add this "clock" object to the document packet with exactly those values — do not omit it.
- "range": "LOOP_STOP" loops back to the interval start when it reaches the end; "CLAMPED" holds at the end time; "UNBOUNDED" keeps advancing past the end.
- "step": "SYSTEM_CLOCK_MULTIPLIER" (the default) advances "currentTime" by "multiplier" times the elapsed real (wall-clock) time between ticks — use this unless the intent asks for a different stepping mode.
Example: named document metadata with a clock and one entity
[
{
"id": "document",
"name": "Vehicle Tracking",
"version": "1.0",
"clock": {
"interval": "2012-03-15T10:00:00Z/2012-03-16T10:00:00Z",
"currentTime": "2012-03-15T10:00:00Z",
"multiplier": 60,
"range": "LOOP_STOP",
"step": "SYSTEM_CLOCK_MULTIPLIER"
}
},
{
"id": "pt-1",
"position": { "cartographicDegrees": [5, 15, 0] },
"point": { "pixelSize": 10, "color": { "rgba": [255, 255, 255, 255] } }
}
]
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.
- 1mo ago First seen · 45 lines · 56 tokens per session scan A c4f48e5c7786
czml-clock is a skill published in the GitHub repository CesiumGS/cesiumjs-ai-starter-app (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 529 once invoked, about $0.0002 per session on Opus 5.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
QGIS Processing
Use Arion's local QGIS integration to discover, describe, and run qgisprocess workflows against file-backed layers. Use when a request involves QGIS Processing algorithms, qgisprocess troubleshooting, chaining multiple QGIS steps, or selecting the right algorithm and parameters for a map layer.
CRS Sanity Check
Validate coordinate systems, units, and reprojection assumptions before analysis.
Data Source Intake
Standard intake checklist for evaluating geospatial data sources before use.
Geospatial Triage
Rapidly scope a geospatial request, validate data assumptions, and propose an execution plan.
latex-compile
Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…
nb-to-wolfbook
Convert Mathematica .nb or .m files to Wolfbook .wb format so they open and run in VS Code. Use when bringing existing .nb/.m files into Wolfbook, or to make an existing .wb bridge-safe.