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 clawdotnet/openclaw.net --skill nacos-router-weather-retrygit clone --depth 1 https://github.com/clawdotnet/openclaw.netWrote 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/clawdotnet/openclaw.net/nacos-router-weather-retry)<a href="https://agentmods.dev/skills/clawdotnet/openclaw.net/nacos-router-weather-retry"><img src="https://agentmods.dev/badge/skills/clawdotnet/openclaw.net/nacos-router-weather-retry/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/clawdotnet/openclaw.net/nacos-router-weather-retry"><img src="https://agentmods.dev/badge/skills/clawdotnet/openclaw.net/nacos-router-weather-retry.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.00023 | $0.00314 |
| Opus 5.5 | $0.00009 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
nacos-router-weather-retry 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
Opt-in contract fixture for #233: the capability step permits up to three attempts (100 ms backoff) only when the host marks weather-mcp/get_weather retry-safe. The test harness opts in for its read-only fixture. Default Nacos composition does not assume retry safety and takes the fallback after the first failure. No model call is needed.
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 · 39 lines · 23 tokens per session scan A 0c9f84cf623e
nacos-router-weather-retry is a skill published in the GitHub repository clawdotnet/openclaw.net (527 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 314 once invoked, about $0.0001 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-09-19.
Other skills, from other repositories
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
live-verification-discipline
Governs how Xeo Forge features are declared complete. Use when finishing any fix or feature — no claim of "done" is valid without a live probe (real API response, DB row content, or captured behavior) attached as evidence. Text descriptions of intent are never evidence.
csharp-testing
C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.
csharp-testing
C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.