Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/UvRoxx/midnight-agent-skillsnpx agentmods add skills/uvroxx/midnight-agent-skills/midnight-deployWrote 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/uvroxx/midnight-agent-skills/midnight-deploy)<a href="https://agentmods.dev/skills/uvroxx/midnight-agent-skills/midnight-deploy"><img src="https://agentmods.dev/badge/skills/uvroxx/midnight-agent-skills/midnight-deploy/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/uvroxx/midnight-agent-skills/midnight-deploy"><img src="https://agentmods.dev/badge/skills/uvroxx/midnight-agent-skills/midnight-deploy.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.00061 | $0.01322 |
| Opus 5 | $0.00030 | $0.00661 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
midnight-deploy scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --proto '=https' --tlsv1.2 -LsSf \ How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Midnight Deploy
Deploy Midnight smart contracts to local development environment or preview network (testnet).
When to Use
Use this skill when:
- Deploying a new Compact contract
- Starting local Midnight infrastructure
- Connecting to preview network (testnet)
- Troubleshooting deployment issues
- Setting up development environment
How It Works
- Compiles Compact contract to WebAssembly + ZK circuits
- Starts required infrastructure (node, indexer, proof server)
- Deploys contract with initial state
- Returns contract address for frontend integration
Prerequisites
Before deploying, ensure you have:
# Check Compact compiler
compact check
# Check Node.js
node -v # v23+
# Check Docker (for local infrastructure)
docker -v
Local Development (Standalone)
Start Local Infrastructure
# From project root
npm run setup-standalone
This starts:
- Midnight Node:
ws://127.0.0.1:9944 - Indexer:
http://127.0.0.1:8088 - Proof Server:
http://127.0.0.1:6300
Deploy to Local
# Build contract first
cd counter-contract
npm run build
# Deploy via CLI
cd ../counter-cli
npm run deploy:local
Preview Network (Testnet)
Configure Environment
Create counter-cli/.env:
MY_PREVIEW_MNEMONIC="your twelve word mnemonic phrase here"
MY_UNDEPLOYED_UNSHIELDED_ADDRESS=""
Get Test Tokens
- Visit Midnight Faucet
- Enter your wallet address
- Receive tSTAR tokens
Deploy to Preview
# Build contract
cd counter-contract
npm run build
# Deploy to testnet
cd ../counter-cli
npm run deploy:preview
Deployment Output
Successful deployment returns:
{
"contractAddress": "0x1234567890abcdef...",
"deploymentTxHash": "0xabcdef1234567890...",
"network": "preview",
"timestamp": "2024-01-15T10:30:00Z"
}
Configure Frontend
After deployment, update frontend environment:
# frontend-vite-react/.env
VITE_CONTRACT_ADDRESS="0x1234567890abcdef..."
What ships with it
1 file 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.
- 10d ago First seen · 236 lines · 61 tokens per session scan A fa5a65c18013
midnight-deploy is a skill published in the GitHub repository UvRoxx/midnight-agent-skills (9 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 1,322 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
midnight-network
Guide to Midnight Network infrastructure, validators, indexers, and network operations. Use when users need to run Midnight validators and participate in consensus, set up and configure Midnight indexers for blockchain data, configure network nodes and infrastructure, monitor validator performance and network health…
cli-anything-eth2-quickstart
Use eth2-quickstart to autonomously deploy a hardened Ethereum node, install execution and consensus clients, configure validator metadata, expose RPC safely, and inspect node health with structured JSON output.
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
skill0
Root index of x-cmd skill0 sub-skills. Defines the OKR-style agent workflow (goal → rule-verified results → execute), skill discovery, and agent tooling preferences. Style: principle-first, concise, delegate specifics to authoritative external sources.
multichain-deployment
Use when deploying the same protocol to multiple chains at the same address. Covers CREATE2 for deterministic addresses, deployment registries, chain-specific configuration, multi-chain testing, and canonical deployment patterns.
l2-deployment
Use when deploying contracts to L2 networks (Base, Optimism, Arbitrum). Covers L2-specific considerations, PUSH0 compatibility, gas estimation, L1 data costs, bridge integration, and deployment scripts.