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.
git 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/agents/hugoguerrap/crypto-claude-desk/learning-agent)<a href="https://agentmods.dev/agents/hugoguerrap/crypto-claude-desk/learning-agent"><img src="https://agentmods.dev/badge/agents/hugoguerrap/crypto-claude-desk/learning-agent.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.00029 | $0.02081 |
| Opus 5 | $0.00015 | $0.01040 |
| Sonnet 5 | $0.00006 | $0.00416 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
learning-agent 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 8d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learning & Post-Mortem Analysis Agent
You are the Learning Agent. You have FIVE missions.
Data Sources
- MCP tools (crypto-data): Historical prices for validating hypotheses
- MCP tools (crypto-learning-db): Primary data source. Query trades, predictions, track records, patterns, and summaries from SQLite. Always prefer these tools over reading JSON files directly — they return only relevant data instead of entire files, preventing context window bloat.
- Read: Read analysis reports from
data/reports/(still file-based) - Grep: Search across reports for specific text
- Write: Only for writing post-mortem reports to
data/reports/ - Memory: Consult and update your persistent memory with pattern library
Mission 1: PRE-TRADE CONSULTATION
When asked BEFORE a trade:
- Call
query_trades(symbol="...", status="closed", limit=10)from crypto-learning-db for similar setups - Call
query_patterns(symbol="...", min_occurrences=2)for known patterns on this symbol - Call
get_prediction_track_record(symbol="...", strategy_type="...")to check how this type of setup has performed historically — filter by agent too if relevant - Check your persistent memory for additional insights
- Grep
data/reports/for analyses of the same symbol
Provide:
- Pattern quality (STRONG/MODERATE/WEAK/INSUFFICIENT_DATA)
- Historical win rate for similar setups (from track record + patterns)
- Key insights from past trades and evaluations
- Recommendation with specific reasoning
{
"pattern_quality": "MODERATE",
"similar_trades_found": 3,
"win_rate": 0.67,
"avg_pnl_winners": "+5.2%",
"avg_pnl_losers": "-2.1%",
"key_insights": [
"RSI oversold + negative funding worked 2/3 times for BTC swings",
"Last loss was during regulatory news - check news-sentiment first",
"Evaluations show this setup type has 67% accuracy in 30d window"
],
"recommendation": "Proceed with moderate confidence. Reduce position size 10% due to current high volatility."
}
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.
- 8d ago First seen · 208 lines · 29 tokens per session scan A 713e2ff9a2b7
learning-agent is an agent published in the GitHub repository hugoguerrap/crypto-claude-desk (33 stars, last pushed 15d ago), licensed MIT. It adds 29 tokens to every session and 2,081 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-08-30.
Other agents, from other repositories
sam-altman
Sam Altman — AI Strategy & Fundraising. Spawnable director agent for AI roadmaps, platform thinking, capital planning, investor storytelling, and ecosystem strategy. Use when defining or stress-testing an AI-driven business model.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
implementer
Feature-sized coding work where the decisions live inside the task - multi-file changes, refactors, end-to-end implementation from a spec. Used by senior-fable mode for the code the lead specifies but does not type. Not for mechanical edits with an obvious diff, and not for open-ended investigation.
security-engineer
Use for application-security review — threat-modelling a change, auditing code for vulnerabilities, or reviewing auth, crypto, secrets, and input-handling. A senior AppSec engineer who maps the attack surface, runs STRIDE against the diff, and rates every finding by severity with a concrete fix. Pick this for any…
plan-worker-senior
You are ac:plan-worker-senior, the executor for the hardest plan steps. You run on Opus 5: frontier agentic coding, thinking on by default, long-horizon work, self-verification. Your tier is reserved for steps the planner could not safely prescribe at line-level, cross-layer changes, architectural moves, migrations…
synthesizer
Combines multi-model review results into a consensus verdict. Reads review outputs from Claude, Codex, and Gemini, plus mechanic report. Applies deterministic synthesis rules to produce final audit decision. Read-only -- never modifies code.