Borrowing it
Nothing to install: this file belongs to reloru/new-relo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/reloru/new-relo/main/.claude/skills/verify-site/SKILL.mdgit clone --depth 1 https://github.com/reloru/new-reloWrote 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/reloru/new-relo/verify-site)<a href="https://agentmods.dev/skills/reloru/new-relo/verify-site"><img src="https://agentmods.dev/badge/skills/reloru/new-relo/verify-site.svg" alt="Measured on agentmods" 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.00053 | $0.02597 |
| Opus 5 | $0.00026 | $0.01299 |
| Sonnet 5 | $0.00011 | $0.00519 |
| Haiku 4.5 | $0.00005 | $0.00260 |
Grade B, and why
verify-site scanned grade B with 2 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 7d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s "$BASE/api/health" | python3 -m json.tool Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Health-check the live crosbynews.com deploy with curl — every content page in BOTH languages returns 200 and is substantive, security headers present, canonical redirects are one hop, markdown negotiation wo How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify the live site
Confirm the deployed site is healthy. Use the base URL in $ARGUMENTS if one was
given, otherwise https://crosbynews.com. Run the checks below with curl, then
report a compact PASS/FAIL table. For anything that FAILs, quote the actual
status/header so it's actionable.
Deploys land in ~10–40s but take 1–2 minutes to reach every edge. A single
curl can be served by a colo still running the PREVIOUS Worker version, and a
?cb= cache-buster does NOT help — this is version propagation, not caching.
When checking that a specific change went live, sample ~8 times and require
agreement before reporting either way:
for i in $(seq 1 8); do curl -s "$BASE$PATH?cb=$RANDOM-$i" | grep -c "$MARKER"; done
Measured 2026-08-05: 7/8 new, 1/8 old, persisting ~2 minutes past a green deploy job. Report a mixed sample as "still propagating", never as a failure.
1. Routes return 200 — both languages, every page
Sweep all 21 content pages in BOTH languages. Not a spot-check. Roughly half
the site's render branches never execute under lang="en", so an English-only
pass proves nothing about /es. This is not hypothetical: /es/hourly served a
502 in production across two deploys because features/hourly.js referenced
ES_NWS_NOTE, which only the Spanish branch reaches, and the checklist here said
"/es (Spanish spot-check)" — so /es was green while /es/hourly was down.
English pages: /, /weather, /hourly, /radar, /alerts, /water,
/fishing, /tropics, /pollen, /air, /traffic, /news, /calendar,
/burn-ban, /emergency, /about, /developers, /privacy, /contact, /sitemap, /mcp.
Spanish: the same 21 under /es — /es, /es/weather, … /es/sitemap,
/es/mcp. (/es is the hub, not /es/.)
Non-page routes: /robots.txt, /sitemap.xml, /llms.txt,
/api/weather, /api/health, /api/news, /api/calendar, /api/water,
/api/fishing, /api/tropics, /api/pollen, /api/burn-ban, /api/air, /api/traffic,
/alerts.xml, /news.xml, /badge.svg,
/manifest.json, /icon.svg, /sw.js, /favicon.svg, /favicon.ico,
/apple-touch-icon.png, /radar-image,
/.well-known/api-catalog, /openapi.json, /.well-known/security.txt,
/.well-known/mcp/server-card.json, /.well-known/agent-skills/index.json,
/.well-known/agent-skills/crosby-weather/SKILL.md.
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.
- 7d ago First seen · 187 lines · 53 tokens per session scan B bb765011ab8d
verify-site is a skill published in the GitHub repository reloru/new-relo (1 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,597 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, 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
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
Edge Computing Testing
Testing edge computing deployments including latency verification, edge function testing, CDN worker testing, and geo-distributed test execution.
front-vitest
Depth for Vitest tests of front- React 19 SPAs when DOM, RTL, TanStack Query hooks, or TanStack Router route-tree tests are needed. USE WHEN: adding jsdom or testing-library, writing tsx render or renderHook tests, testing createMemoryHistory plus RouterProvider, Suspense UI, or React 19 act fixtures. DO NOT USE WHEN…
playwright
Skill "playwright" from ashish7802/awesome-api-skills, covering playwright skill, ecosystem graph, quick start, production patterns and auto-waiting and locators.
review-vitest
Vitest review (@repo/vitest-config node/workers presets, Cloudflare Vitest pool, testing split) against current official Vitest and Cloudflare best practices. USE WHEN: user runs /review-vitest or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
agent-mailbox
Create and use disposable, token-scoped email addresses through a configured Agent Mailbox MCP server. Use for testing signups, email verification, magic links, password resets, one-time codes, inbound messages, attachments, and transactional email flows.