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 hugoguerrap/crypto-claude-desk --skill monitorgit clone --depth 1 https://github.com/hugoguerrap/crypto-claude-deskWrote 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/hugoguerrap/crypto-claude-desk/monitor)<a href="https://agentmods.dev/skills/hugoguerrap/crypto-claude-desk/monitor"><img src="https://agentmods.dev/badge/skills/hugoguerrap/crypto-claude-desk/monitor/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/hugoguerrap/crypto-claude-desk/monitor"><img src="https://agentmods.dev/badge/skills/hugoguerrap/crypto-claude-desk/monitor.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.00042 | $0.01126 |
| Opus 5 | $0.00021 | $0.00563 |
| Sonnet 5 | $0.00008 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
monitor 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 10d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor - Autonomous Learning Loop
Closes the autonomous loop: check trades, close hits, evaluate predictions, generate summaries.
All agents use subagent_type: general-purpose with explicit model to ensure MCP tool access. Include "Do NOT use the Edit tool" in every prompt.
Workflow
Step 1: Get Current Prices
Delegate using Task with subagent_type: general-purpose, model: haiku:
"You are the market-monitor agent. Get current prices for ALL symbols that have open trades. Call get_portfolio_state() from crypto-learning-db first to see which symbols have open positions. Then use get_exchange_prices(symbol=...) from crypto-exchange MCP to get live prices for each symbol. Return a JSON object like: {"BTC/USDT": 98500, "ETH/USDT": 3200} Do NOT use the Edit tool."
Step 2: Check Open Trades Against SL/TP
Using the prices from Step 1 and the open trades from get_portfolio_state():
For each open trade, check:
- Long trade: Did price drop to or below
stop_loss? Did price rise to or abovetake_profit? - Short trade: Did price rise to or above
stop_loss? Did price drop to or belowtake_profit?
If SL or TP was hit, delegate using Task with subagent_type: general-purpose, model: opus:
"You are the portfolio-manager agent. Close trade {trade_id}. Current price is ${price}. The {SL/TP} at ${level} was hit. Call close_trade(trade_id='{trade_id}', exit_price={price}, close_reason='{SL/TP} hit at ${level}') from crypto-learning-db. Do NOT use the Edit tool."
Step 2b: Trailing Stop Adjustment
For open trades that were NOT closed (still active), check if the trade is profitable:
- Long: current price > entry_price
- Short: current price < entry_price
If profitable AND the current stop_loss hasn't been optimally trailed, delegate using Task with subagent_type: general-purpose, model: sonnet:
"You are the risk-specialist agent. Read agents/risk-specialist.md for context. Trade {trade_id} ({symbol}, {side}) is profitable. Entry: ${entry}, Current: ${price}, SL: ${stop_loss}, TP: ${take_profit}. Analyze whether to trail the stop-loss. Use calculate_volatility(symbol=...) and get_support_resistance(symbol=...) from crypto-technical MCP. If you recommend adjusting, call update_trade(trade_id='{trade_id}', stop_loss={new_sl}, notes='your reasoning') from crypto-learning-db. Rules: only trail in profitable direction, never widen the stop, leave room for normal volatility. Do NOT use the Edit tool."
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.
- 10d ago First seen · 97 lines · 0 tokens per session scan A 547611032c3b
monitor is a skill published in the GitHub repository hugoguerrap/crypto-claude-desk (33 stars, last pushed 17d ago), licensed MIT. It adds 42 tokens to every session and 1,126 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
fintech-expert
Expert in financial technology, payment processing, open banking APIs, PSD2, blockchain in finance, robo-advisors, and RegTech. Use when the user mentions payments, open banking, PSD2, blockchain, cryptocurrency, or robo advisor, or when the task involves Payment Processing, Blockchain in Finance, Payment Security, or…
moss-trade-bot-factory-1.0.25-beta
A tool for turning a trading idea written in everyday language into a cryptocurrency trading bot. It can run local tests on past market data, with optional checks and simulated trades through external platforms.
moss-trade-bot-factory-1.0.3
A tool for turning a trading idea written in everyday language into a cryptocurrency trading bot. It can run local tests on past market data, with optional checks and simulated trades through external platforms.
moss-trade-bot-factory-1.0.24-beta
A tool for turning a trading idea written in everyday language into a cryptocurrency trading bot. It can run local tests on past market data, with optional checks and simulated trades through external platforms.
moss-trade-bot-factory-1.0.24-dev
A tool for turning a trading idea written in everyday language into a cryptocurrency trading bot. It can run local tests on past market data, with optional checks and simulated trades through external platforms.
moss-trade-bot-factory-1.0.24
A skill that creates cryptocurrency trading bots from natural-language descriptions of trading styles. It can run local backtests and support repeated strategy reflection; external validation or simulated trading may be available when connected.