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 SaucePackets/bdk-dojo-skill --skill bdk-dojogit clone --depth 1 https://github.com/SaucePackets/bdk-dojo-skillWrote 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/saucepackets/bdk-dojo-skill/bdk-dojo)<a href="https://agentmods.dev/skills/saucepackets/bdk-dojo-skill/bdk-dojo"><img src="https://agentmods.dev/badge/skills/saucepackets/bdk-dojo-skill/bdk-dojo/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/saucepackets/bdk-dojo-skill/bdk-dojo"><img src="https://agentmods.dev/badge/skills/saucepackets/bdk-dojo-skill/bdk-dojo.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.03493 |
| Opus 5 | $0.00033 | $0.01747 |
| Sonnet 5 | $0.00013 | $0.00699 |
| Haiku 4.5 | $0.00007 | $0.00349 |
Grade A, and why
bdk-dojo 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 9d 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDK Dojo
⚠️ LOAD FIRST — before any BDK Dojo turn
BDK Dojo is a teaching skill. It depends on teach-mode. Load it before you do anything else:
skill_view(name="teach-mode")
teach-mode gives you the hint ladder: orient → rails → hint → snippet → review → rescue.
It also now includes the language-bridge technique, concrete analogies, coding review formats, and language policy that were previously in coding-dojo-teach-mode.
If you skip this load step, you will over-help. Load teach-mode now.
Overview
BDK Dojo is a learning-first workflow for Bitcoin wallet engineering practice.
It uses small Rust exercises to teach the concepts behind wallet libraries like BDK: UTXOs, descriptors, PSBTs, wallet sync, fee estimation, ownership, error handling, and test discipline.
The goal is not to pretend the learner is ready to patch BDK on day one. The goal is to build the habits that make future contribution credible: small changes, readable code, tests, clear questions, and accurate mental models.
Required Companion Skills
BDK Dojo requires one standalone skill. Load it before every session:
teach-mode— the learner-first contract, hint ladder, understanding gates, language-bridge techniques, coding review formats, and language policy.
If teach-mode is missing, BDK Dojo degrades into answer-dumping. Load it before the first lesson handoff.
When to Use
Use this skill when the user asks for:
- a BDK Dojo lesson
- Bitcoin/Rust practice
- wallet engineering exercises
- BDK concept explanations
- UTXO, descriptor, PSBT, sync, or fee-estimation katas
- preparation for Bitcoin open-source contribution
- meetup-friendly Bitcoin developer lessons
Do not use this for:
- real wallet security decisions
- production key handling
- signing real transactions
- legal, tax, or investment advice
- replacing the official BDK documentation
Core Stance
Load and follow the standalone umbrella teach-mode skill. BDK Dojo treats Teach Mode as an external dependency, not a vendored copy, so multiple dojo skills can share the same canonical learner-first contract. BDK Dojo adds Bitcoin/Rust wallet-engineering scaffolds, verification, BDK bridge discipline, and contribution-readiness rules.
What ships with it
10 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.
- references/answer-validation.md 3.6 KB
- references/bdk-learning-coverage.md 4.7 KB
- references/bdk-teach-mode-supplement.md 8.3 KB
- references/bitcoin-dojo-format.md 5.5 KB
- references/context-discipline.md 1.9 KB
- references/course-spine.md 12 KB
- references/lesson-template.md 768 B
- references/progress-journal.md 2.4 KB
- references/teacher-style.md 5.3 KB
- references/wallet-balance-utxo-model.md 3.1 KB
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.
- 9d ago First seen · 403 lines · 66 tokens per session scan A fab622765011
bdk-dojo is a skill published in the GitHub repository SaucePackets/bdk-dojo-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 3,493 once invoked, about $0.0003 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-31.
Other skills, from other repositories
smart-contract-reading-guide
How to read and understand smart contracts — navigating Etherscan, reading Solidity code, understanding ABIs, decoding transactions, and spotting common patterns. Use when helping users verify contracts, understand DeFi protocol mechanics, or decode on-chain activity.
web3-glossary
Comprehensive Web3 and DeFi glossary — definitions for 150+ terms covering blockchain, DeFi, NFTs, DAOs, L2s, and crypto culture. Use when a user asks what a term means or needs jargon explained in plain language.
skmtc-operation
The operation-generator shape for Skmtc: one definition per (path, method), for any output family — client hooks, SDK methods, forms, route stubs, docs. Output varies wildly; the DECOMPOSITION of the operation and the peer-consumption rules do not. Core teaching: every schema that appears in your output is a reference…
okx-guide
Onchain OS onboarding & guide hub — the single entry for first-time, 'what is this / how do I use it', OKX.AI, and customer-support intents; classifies the intent and routes to the right sub-flow via its Intent Routing table. Covers: (1) Onchain OS onboarding + welcome banner — 'what is onchainos', 'what is onchain…
wallets
Educational reference on Ethereum wallet types — EOAs, smart contract wallets, multisig (Safe), account abstraction (ERC-4337). Use when explaining wallet concepts, choosing a wallet architecture, or designing key management. NOT for sending transactions — use ethereum-local-wallet for that.
solana-beginner
Teach Solana fundamentals to developers new to the ecosystem. Use when a user says "what is Solana", "why Solana", "new to Solana", "explain Solana to me", "Solana basics", "EVM to Solana", "getting started with Solana", or "Solana fundamentals". Adapts to user's background — EVM devs, backend devs, or complete…