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 routergit 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/router)<a href="https://agentmods.dev/skills/alsk1992/cloddsbot/router"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/router/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/router"><img src="https://agentmods.dev/badge/skills/alsk1992/cloddsbot/router.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.01514 |
| Opus 5 | $0.00006 | $0.00757 |
| Sonnet 5 | $0.00003 | $0.00303 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
router 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Router - Complete API Reference
Route orders to the best platform based on price, liquidity, fees, and execution quality.
Chat Commands
Route Order
/route "Trump 2028" YES 1000 Find best route for $1000
/route BTCUSDT long 0.5 Route futures order
/route --mode best-price "Fed" YES Optimize for price
/route --mode best-liquidity ... Optimize for fills
Compare Routes
/route compare "Trump" YES 1000 Compare all platforms
/route fees "Trump" Compare fee structures
/route liquidity "Trump" Compare orderbook depth
Execution
/route execute <route-id> Execute routed order
/route split "Trump" YES 5000 Split across platforms
TypeScript API Reference
Create Smart Router
import { createSmartRouter } from 'clodds/router';
const router = createSmartRouter({
// Supported platforms
platforms: ['polymarket', 'kalshi', 'manifold'],
// Default mode
defaultMode: 'balanced',
// Fee structures
fees: {
polymarket: { maker: -0.005, taker: 0.01 },
kalshi: { maker: 0, taker: 0.01 },
manifold: { maker: 0, taker: 0 },
},
});
Find Best Route
const route = await router.findBestRoute({
market: 'trump-win-2028',
side: 'YES',
size: 1000,
mode: 'best-price', // 'best-price' | 'best-liquidity' | 'lowest-fee' | 'balanced'
});
console.log(`Best platform: ${route.platform}`);
console.log(`Expected price: ${route.expectedPrice}`);
console.log(`Expected slippage: ${route.expectedSlippage}%`);
console.log(`Fees: $${route.fees}`);
console.log(`Net cost: $${route.netCost}`);
console.log(`Fill probability: ${route.fillProbability}%`);
Compare All Platforms
const comparison = await router.compare({
market: 'trump-win-2028',
side: 'YES',
size: 1000,
});
console.log('Platform Comparison:');
for (const platform of comparison) {
console.log(`\n${platform.name}:`);
console.log(` Price: ${platform.price}`);
console.log(` Liquidity: $${platform.liquidity}`);
console.log(` Slippage: ${platform.slippage}%`);
console.log(` Fees: $${platform.fees}`);
console.log(` Net cost: $${platform.netCost}`);
console.log(` Score: ${platform.score}`);
}
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 · 234 lines · 13 tokens per session scan A 5413223788a3
router 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 1,514 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…