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/dirtybits/agent-skills/web3-protocol-designnpx skills add dirtybits/agent-skills --skill web3-protocol-designgit clone --depth 1 https://github.com/dirtybits/agent-skillsWrote 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/dirtybits/agent-skills/web3-protocol-design)<a href="https://agentmods.dev/skills/dirtybits/agent-skills/web3-protocol-design"><img src="https://agentmods.dev/badge/skills/dirtybits/agent-skills/web3-protocol-design.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 | $0.00064 | $0.01733 |
| Opus 5 | $0.00032 | $0.00866 |
| Sonnet 5 | $0.00013 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
web3-protocol-design 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 4d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web3 Protocol Design
When To Use
Use this skill when the task involves:
- designing a new web3 protocol or protocol feature
- reviewing tokenomics, fees, staking, rewards, slashing, or dispute flows
- specifying smart contract state, permissions, or account models
- choosing on-chain, off-chain, oracle, bridge, or keeper boundaries
- preparing a protocol spec, audit brief, test plan, or launch checklist
Design Workflow
- Define the protocol goal in one sentence, then list explicit non-goals.
- Identify actors, assets, chains, contracts, off-chain services, and external dependencies.
- Map the lifecycle as state transitions: initialization, normal use, settlement, recovery, upgrade, and shutdown.
- Specify trust assumptions for admins, signers, sequencers, bridges, oracles, keepers, governance, and users.
- Design incentives with concrete flows: who pays, who receives, when funds move, what can be slashed, and what can be extracted.
- Write invariants before implementation details. Treat every invariant as a future test or monitor.
- Threat-model the design against economic, technical, governance, liquidity, oracle, and UX failures.
- Define launch gates: tests, simulations, audits, monitoring, limits, emergency controls, and rollout stages.
Delivery And Activation Stages
Track design lock, implementation, merge, deployability, deployment and verification, client/operator configuration, feature activation, live smoke, and public launch approval as separate states. Do not use “complete,” “deployed,” or “live” interchangeably.
- For a gated mechanism, specify the disabled/default state, enabling authority, dependent contracts and clients, operational inputs, monitoring, rollback, and evidence required to advance each state.
- Treat user entry points, claim or exit paths, operator runbooks, custody and role assignments, address/config distribution, and live-flow verification as activation deliverables rather than incidental follow-up work.
- Revalidate the candidate after prerequisite merges or deployment changes. Prior checks against an older head, base, address, or compiler artifact do not certify the resulting release.
- On a non-production network with no live liabilities, prefer an explicitly approved clean break when it removes migration and compatibility machinery. Record the state, clients, addresses, and fixtures that the break invalidates.
What ships with it
3 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.
- 4d ago First seen · 157 lines · 64 tokens per session scan A c86a842d09fc
web3-protocol-design is a skill published in the GitHub repository dirtybits/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,733 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
tokenomics
Token economic design authority — supply schedules, emission curves, vesting and cliff structures, bonding curves, liquidity bootstrapping pools, governance token design, veToken and vote-escrowed models, staking reward mechanics, token sink design, incentive alignment analysis, and Gini coefficient distribution…
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.12.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
TRX Staking & SR Voting
Stake TRX, vote for Super Representatives, and claim voting rewards on TRON.
conducting-cyber-risk-assessment-with-nist-800-30
Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk…
blockchain-management
Use this skill when asked about blockchain project management, DAO governance, multi-sig operations, treasury management, tokenomics design, and web3 project methodology. Languages: Solidity, TypeScript, Python. Covers DAO governance frameworks (Compound Governor, Aave, Snapshot, Tally), multi-sig wallet operations…
crypto-report
Analyze cryptocurrency projects with tokenomics, on-chain metrics, and market analysis. Generate comprehensive crypto research reports.