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 skills/worldclockpro/worldclock-mcp/world-clocknpx skills add worldclockpro/worldclock-mcp --skill world-clockgit clone --depth 1 https://github.com/worldclockpro/worldclock-mcpWhat 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.00104 | $0.01063 |
| Opus 5 | $0.00052 | $0.00531 |
| Sonnet 5 | $0.00021 | $0.00213 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
world-clock 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 2d 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.
install: "MCP endpoint: https://worldclock.pro/mcp (Streamable HTTP, no auth). No MCP client? The skill includes a curl fallback." How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
World Clock
Live time facts from worldclock.pro. Never answer timezone questions from memory: DST rules change, offsets are political, and wall-time math has edge cases. The server is public, read-only, and needs no key: https://worldclock.pro/mcp
Pick the right tool
| Question shape | Tool |
|---|---|
| What time is it in X (one or many places, up to 50) | get_current_time |
| It is 9am in A, what time in B, C, D | convert_time with from.dateTime + from.location |
| Express this UTC instant in local times | convert_time with utc |
| Time or timezone at lat/lon | time_by_coordinates |
| Does X observe DST, when do clocks change | get_dst_transitions (optional year) |
| Which city is this, what is its timezone or slug | search_cities |
How to phrase locations
Every location is exactly ONE of:
- query: city name, slug, or alias ("Tokyo", "new-york", "nyc", "Москва", "São Paulo")
- timezone: IANA id ("America/New_York") or abbreviation ("PST", "ET", "UTC")
- latitude + longitude (both required)
Passing two forms at once is an error. For convert_time, pass exactly one of utc or from. Bare datetimes with no zone designator are read as UTC. from.dateTime must look like "2026-06-29T09:00" (local wall time, no zone).
Gotchas the tools handle for you (do not second-guess)
- DST boundaries: always convert on the actual date, not with today's offset. A 9am New York call is a different UTC instant in January and July.
- "EST" is a FIXED offset (UTC-5 year round). "ET" means real New York wall time and follows DST. Prefer "ET" or the IANA id unless the user really means the fixed offset. Same for CST/CT, MST/MT, PST/PT.
- Half and quarter offsets are real: India +5:30, Nepal +5:45, Eucla +8:45. Never round offsets to whole hours.
- Ambiguous city names (San Jose, Hyderabad, Portland): call search_cities first, confirm the country, then pass the returned slug as query.
- Date line: conversions can change the weekday. Report the weekday field from the response, do not infer it.
- Fixed abbreviations report isDST false and no transitions by design.
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.
- 2d ago First seen · 85 lines · 104 tokens per session scan A 8fabae3cd49a
world-clock is a skill published in the GitHub repository worldclockpro/worldclock-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,063 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
prove-a-scanner-fires
Pair every source-scanning hygiene test with a proof that it detects a planted violation, that its walk actually opened files, and that it is no laxer than the tool it mirrors. Use when writing or reviewing any test that greps a crate's own text — citation audits, hardcoded-constant checks, imputation scans…
add-module
Add a new crate to the bioprism workspace implementing a blueprint section, including registering it, choosing dependencies without creating cycles, and the honesty conventions every crate must follow. Use when starting a new module, when asked to cover an uncovered blueprint section, or when setting up work for a…
check-parity
Verify the CPython reference, the eager Rust path and the indexed store still agree byte for byte on a Context Certificate digest. Use after touching canonical serialization, hashing, compiler passes, the store, or any serde configuration, and before any release or wire-format change.
verify-crate
Verify a bioprism crate is genuinely green — tests passing and clippy at zero warnings — and recognise the environment failures that masquerade as test failures. Use before claiming a crate is done, after landing an agent's work, when a test count looks wrong or lower than expected, or when cargo test reports a…
mission-lifecycle
Author, preflight, and execute aurora-agent missions — validated DAGs of MCP tool calls. Use when asked to build or run a mission, when a mission is refused with invalidmission or operationsgateacceptancerequired, when deciding between synchronous agentmission and async submission, or when wiring evaluator reviews and…
aurora-setup
Set up, build, or troubleshoot the AURORA Agent (bioprism) MCP server used by the aurora-agent plugin. Use when the aurora-agent MCP server fails to start, when its tools are missing from a session, when asked to install or build the aurora-agent backend, or when a bioprism build or test behaves strangely on Windows.