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 alsk1992/CloddsBot --skill weathergit clone --depth 1 https://github.com/alsk1992/CloddsBotWrote 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/alsk1992/cloddsbot/weather)<a href="https://agentmods.dev/skills/alsk1992/cloddsbot/weather"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/weather/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/alsk1992/cloddsbot/weather"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/weather.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.00553 |
| Opus 5 | $0.00006 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
weather 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weather Betting
Use NOAA weather forecasts to find edge on Polymarket weather markets.
Commands
/weather scan Scan all weather markets for edge
/weather forecast <city> Get NOAA forecast for a city
/weather markets List active weather markets
/weather edge <market-id> Calculate edge for specific market
/weather bet <market-id> <amount> Execute bet
/weather auto [--threshold 10] Auto-bet on high-edge markets
/weather history View bet history
Examples
/weather forecast "New York"
/weather scan
/weather edge abc123
/weather bet abc123 10
/weather auto --threshold 15
How It Works
- Fetch NOAA Forecast: Get official NWS weather data (free, no API key)
- Match to Markets: Find Polymarket weather markets for the same location/date
- Calculate Edge: Compare NOAA probability to market YES price
- Bet if Edge: If NOAA probability differs significantly from market, bet
Edge Calculation
Edge = NOAA Probability - Market Price
Example:
NOAA says 80% chance of rain in NYC tomorrow
Polymarket "Will it rain in NYC?" YES price: 0.65 (65%)
Edge = 80% - 65% = +15% -> Bet YES
Supported Market Types
- Temperature: "Will NYC exceed 90°F on Saturday?"
- Precipitation: "Will it rain in LA tomorrow?"
- Snow: "Will Chicago get 6+ inches of snow?"
- Record: "Will Phoenix hit a record high this week?"
Confidence Levels
- High: Edge >= 15%, reliable forecast data
- Medium: Edge 10-15%, some uncertainty
- Low: Edge 5-10%, more speculative
Position Sizing
Uses quarter-Kelly criterion for conservative sizing:
Bet Size = Bankroll * (Edge / Odds) * 0.25
Capped at 10% of bankroll per bet.
Supported Cities
Major US cities including: New York, Los Angeles, Chicago, Houston, Phoenix, Philadelphia, San Antonio, San Diego, Dallas, San Jose, Austin, Jacksonville, San Francisco, Seattle, Denver, Washington DC, Boston, Nashville, Detroit, and more.
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.
- 6d ago First seen · 81 lines · 13 tokens per session scan A dde6a82f34a1
weather is a skill published in the GitHub repository alsk1992/CloddsBot (1,190 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 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-03.
Other skills, from other repositories
perp-cli
Multi-DEX perpetual futures trading via the perp-cli command-line tool. Use when user asks to: trade perps, check funding rates, scan/execute arbitrage (perp-perp or spot-perp), run delta-neutral strategies, bridge USDC across chains, manage positions/orders/leverage, deposit/withdraw, hedge spot+perp, trade HIP-3…
hive-market-research
Use this skill for any live crypto market question — prices, 24h moves, liquidity, exchange/venue data, OHLC candles, order books, tickers, funding rates, derivatives, trading context — even casual asks like "what's BTC at" or "is ETH pumping". Use it whenever the answer needs current market numbers instead of memory.…
hive-query
Default entry point for any live crypto question when Hive MCP is connected — prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps. Use it whenever the answer depends on live or on-chain data instead of answering from memory, even if the user never mentions Hive. Routes intent to a…
hive-token-diligence
Use this skill whenever the user asks whether a specific token is real, legit, liquid, well-held, enriched, investable, or worth researching — "is this token a scam", "run diligence on 0x…", "who holds this", "does it have real liquidity" — even if they never say "diligence". Investigates metadata, market context…
hive-defi-research
Use this skill when the user asks about DeFi protocol metrics — TVL, fees, revenue, yields, APY, stablecoin supply, bridge volume, or chain-level DeFi totals — or wants protocols compared ("Aave vs Compound", "top protocols by TVL", "best stablecoin yields"). Use it whenever the answer needs current protocol-level…
hive-dex-pool-analysis
Use this skill when the user asks about a DEX pool or trading pair — liquidity depth, recent swaps/trades, OHLCV candles, trending pools, fee tiers, or token-level DEX flow on a chain — including "how deep is the X/Y pool", "what's trading on Uniswap", or a pasted pair address. For CEX prices, order books, and funding…