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 agentmods add skills/cloudquant/backtrader/jcdbnpx skills add cloudQuant/backtrader --skill jcdbgit clone --depth 1 https://github.com/cloudQuant/backtraderWhat 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 | $0.00118 | $0.01555 |
| Opus 5 | $0.00059 | $0.00777 |
| Sonnet 5 | $0.00024 | $0.00311 |
| Haiku 4.5 | $0.00012 | $0.00155 |
Grade A, and why
jcdb 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 yesterday.
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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
2 files 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.
- yesterday First seen · 121 lines · 118 tokens per session scan A 1af91ebe03ae
jcdb is a skill published in the GitHub repository cloudQuant/backtrader (159 stars, last pushed 10d ago), licensed GPL-3.0. It adds 118 tokens to every session and 1,555 once invoked, about $0.0006 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
options-trading
Use before researching, selecting, opening, modifying, or closing any option position, including single-leg options, vertical spreads, iron condors, butterflies, straddles, strangles, calendars, and other multi-leg structures. Also use when a broad trading mandate leads you to consider options even if the user did not…
stock-trading
Use before researching, selecting, opening, modifying, or closing a stock or ETF position, including discretionary investing, rotation, breakout, momentum, mean-reversion, opening-range breakout, and VWAP trading. Also use when a broad mandate leads you to consider stocks or ETFs even if the user did not name an asset…
varrd-research
The core VARRD research tool — talk to a state-of-the-art quant AI to research, chart, test, optimize, and trade any market idea. Use when the user wants to test a trading hypothesis, find edges, or validate a strategy with real market data.
varrd-discover
Autonomous edge discovery — VARRD generates, tests, and validates trading hypotheses hands-free. Use when the user wants the AI to find trading edges on its own given a topic or market.
varrd-edges
Browse VARRD's validated edge library — see which edges are firing right now, get stats and trade levels, or drill into the full methodology and performance of any edge.
varrd-hypothesis
Get full details on a specific saved strategy — formula, metrics, version history. Use when the user wants to inspect a particular hypothesis or strategy in detail.