Borrowing it
Nothing to install: this file belongs to dashpay/platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dashpay/platform/v5.1-dev/.claude/skills/protocol-upgrade-test/SKILL.mdgit clone --depth 1 https://github.com/dashpay/platformWrote 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/dashpay/platform/protocol-upgrade-test)<a href="https://agentmods.dev/skills/dashpay/platform/protocol-upgrade-test"><img src="https://agentmods.dev/badge/skills/dashpay/platform/protocol-upgrade-test/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/dashpay/platform/protocol-upgrade-test"><img src="https://agentmods.dev/badge/skills/dashpay/platform/protocol-upgrade-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.01872 |
| Opus 5.5 | $0.00036 | $0.00749 |
| Sonnet 5.5 | $0.00018 | $0.00374 |
| Haiku 4.5 | $0.00009 | $0.00187 |
Grade A, and why
protocol-upgrade-test 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 2mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Upgrade Test
Review the consensus path before designing tests. Treat protocol selection, first-block state migration, and release orchestration as separate layers with separate evidence.
Authority
Default to review, which is read-only. It permits local source inspection and
test/report design only. It does not authorize ref fetching, dependency
installation, image pulls, Docker changes, network starts, config migration, or
service restarts.
Use another mode only when the user explicitly requests it:
drive: add and run deterministic Drive/ABCI tests.local-release: operate an isolated local network and release images.snapshot: inspect a supplied state artifact read-only and mutate private copies only.all: union of the explicitly requested modes.
Never broaden authority because a later step would be convenient.
Review workflow
Read references/review-checklist.md before reviewing code.
1. Resolve the comparison
For a released upgrade, require both baseline and target to be exact local
release-tag names. Resolve each tag to its peeled commit SHA and confirm the
Dashmate/package version matches the tag. Do not use a branch, HEAD, or a
mutable remote-tracking ref as evidence for code shipped in release artifacts.
If a tag is missing, stop unless the user explicitly authorizes fetching it.
Run:
.claude/skills/protocol-upgrade-test/scripts/review_transition.sh \
<baseline-tag> <target-tag> [old-protocol] [new-protocol]
For pre-release preparation only, a fetched development branch may be used as a supplemental target:
.claude/skills/protocol-upgrade-test/scripts/review_transition.sh \
--allow-non-tag-target <baseline-tag> <target-ref> \
[old-protocol] [new-protocol]
Pin and report the target SHA and label the result pre-release; it cannot
certify a release or substitute for rerunning the review against the eventual
release tag. Fetching branches or tags still requires explicit user authority.
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.
- 2mo ago First seen · 201 lines · 90 tokens per session scan A a1dd0377774e
protocol-upgrade-test is a skill published in the GitHub repository dashpay/platform (93 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,872 once invoked, about $0.0004 per session on Opus 5.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
solana-dev
Solana development: Anchor and Pinocchio programs, Kit clients, wallet flows, testing. Use when building a Solana dapp or program (e.g. write Anchor escrow, create SPL token, wallet-standard login, debug PDA, deploy to devnet).
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
analyzing-ransomware-payment-wallets
Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware…
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…
blockchain-web3
Use this skill when asked about web3 frontend development, ethers.js, viem, wagmi, web3.js, wallet integration (MetaMask, Phantom, WalletConnect), dApp architecture, RPC providers (Alchemy, Infura), and TypeScript blockchain SDKs. Language: TypeScript. Covers reading blockchain state, sending transactions, wallet…
frontend-design
Create distinctive, production-grade Stellar dApp UI. Combines bold aesthetic direction with smart contract integration patterns — wallet connection flows, transaction UX, contract data displays, and agentic kit hook wiring. No generic "AI slop" aesthetics.