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 signalsgit 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/signals)<a href="https://agentmods.dev/skills/alsk1992/cloddsbot/signals"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/signals/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/signals"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/signals.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.00704 |
| Opus 5 | $0.00006 | $0.00352 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
signals 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signals Trading
Monitor external signals from RSS feeds, Twitter, Telegram, and webhooks to trigger automatic trades.
Commands
/signal add rss <url> [--name "label"] Add RSS feed source
/signal add twitter <username> [--name "label"] Add Twitter/X account
/signal add webhook [--name "label"] Get webhook URL for custom signals
/signal list List all signal sources
/signal remove <id> Remove source
/signal pause <id> Pause source
/signal resume <id> Resume source
/signal history [source] View signal history
/signal test <id> Test signal detection
/signal filter <id> add <type> <value> <action> Add filter rule
/signal filter <id> list List filters
/signal config <id> [options] Configure source
Examples
/signal add rss https://example.com/feed.xml --name "crypto-news"
/signal add twitter CryptoTrader --name "whale-alerts"
/signal add webhook --name "my-alerts"
/signal filter abc123 add keyword "bullish" buy
/signal filter abc123 add keyword "dump" sell
/signal list
Signal Sources
RSS Feeds
Monitor any RSS/Atom feed for signals. Polls every 30 seconds by default.
/signal add rss https://example.com/feed.xml --name "news"
Twitter/X
Monitor tweets from specific accounts via Nitter proxy.
/signal add twitter whale_alert --name "whale"
Webhooks
Receive signals via HTTP POST to a custom webhook URL.
/signal add webhook --name "custom"
# Returns: POST https://clodds.io/webhook/abc123
Webhook payload:
{
"content": "Buy BONK now! 5BqXr...",
"author": "trader",
"secret": "your-secret"
}
Filters
Control when signals trigger trades:
- keyword: Match text content
- mint: Match specific token address
- sentiment: Match bullish/bearish sentiment
- regex: Custom regex pattern
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 · 107 lines · 13 tokens per session scan A 72fd642a6a19
signals is a skill published in the GitHub repository alsk1992/CloddsBot (1,190 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 704 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-wallet-investigation
Use this skill whenever the user wants to look inside a wallet or address — portfolio, holdings, balances, transfers, PnL, NFT exposure, DeFi positions, whale moves, "what does this address hold", "trace this wallet's activity" — even if they just paste an address. Requires wallet address and chain before executing…
hive-tool-discovery
Use this skill when the exact Hive MCP tool, task toolset, provider, endpoint name, schema, operation type, or argument shape is unknown and hive-query routing was not enough — including "what can Hive do", "which provider covers X", "is Hive healthy", or any failed tool-name guess. Discover first with compact Hive…