Validate the development environment for Odra smart contract development. Use when the user says "check env", "check setup", "check prerequisites", "verify environment", or "check-env".
Deploy contracts to a Casper network (nctl, testnet, or mainnet). Use when the user says "deploy", "deploy to livenet", "deploy to nctl", "deploy to testnet", "deploy to mainnet", "run on livenet", or "deploy-to-livenet".
Extract keys from a running NCTL node and create the .env.nctl file. Use when the user says "setup nctl", "configure nctl", "setup-nctl", or "create nctl env".
Run unit and integration test on in-memory OdraVM or (and) real WASMs on CasperVM and report results. Use when the user says "test contract", "verify contract(s)", "unit test".
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin marketplace for distributing plugins related to Odra — a Rust-based smart contract framework for Casper Network.
Streamlines smart contract development with the Odra framework. Gives Claude Code deep knowledge of Odra's APIs, patterns, and tooling so it can help you scaffold, build, and test Odra contracts more effectively.
Add the marketplace and install the plugin:
/plugin marketplace add odradev/odradev-plugins
/plugin install odra-plugin@odradev-plugins
To verify it's active:
/plugin list
Pull the latest version of the marketplace and its plugins:
/plugin marketplace update
The plugin ships with a .mcp.json that enables the Context7 MCP server for up-to-date library documentation lookups. The API key is read from an environment variable — set it before starting Claude Code:
export CONTEXT7_API_KEY=<your-key>
Add this to your shell profile (e.g. ~/.zshrc) to make it permanent.
To make the plugin available automatically for everyone working on your Odra project, add this to .claude/settings.json in your repository:
{
"extraKnownMarketplaces": {
"odradev-plugins": {
"source": {
"source": "github",
"repo": "odradev/odradev-plugins"
}
}
}
"enabledPlugins": {
"odra-plugin@odradev-plugins": true
}
}
Anyone who clones the repo and trusts the project folder will be prompted to install the plugin.
.claude-plugin/
marketplace.json # Marketplace catalog
plugins/
odra-plugin/ # The Odra development plugin
README.md
MIT
npx claudepluginhub odradev/odradev-plugins --plugin odra-pluginBlockchain development with Solidity security, DeFi protocols, NFT standards, and Web3 testing
Blockchain development agents providing expertise in blockchain architecture, smart contracts, and Web3
Specialized agents for blockchain development, smart contracts, and Web3 applications
Skills for secure smart contract development with OpenZeppelin Contracts libraries
Scaffold and develop Oclif CLIs for Midnight Compact smart contracts. Includes a complete CLI template with wallet management, contract deployment, devnet control, and an AI agent for ongoing development.
Full dev lifecycle for OP_NET Bitcoin L1 projects: idea → challenge → spec → build → review → ship. Self-learning across sessions with pattern extraction, agent performance scoring, score-based finding routing, project-type profiles, cross-layer validation, and starter templates. Includes shell-enforced E2E testing gates, frontend runtime smoke checks, PUA problem-solving methodology, the OP_NET Bible (2000+ lines), cross-agent critique, adversarial auditing, adversarial E2E testing, ABI-lock checkpoints, findings ledger with regression tracking, acceptance test generation, chain probe, hard gate enforcement, incremental audits, dry-run mode, execution tracing, dynamic re-planning from learned patterns, dynamic knowledge slice loading, property-based fuzz testing, stale pattern pruning, mutation testing as loop exit gate, structured repair phases (R1/R2/R3), goal-oriented build evaluation, hierarchical repo map, autoresearch optimize mode, and TLA+ formal specification verification as a pre-codegen phase. Agents get smarter with every project.