Borrowing it
Nothing to install: this file belongs to mesutgulecen/ponscli. 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/mesutgulecen/ponscli/main/.claude/skills/verify/SKILL.mdgit clone --depth 1 https://github.com/mesutgulecen/ponscliWrote 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/mesutgulecen/ponscli/verify)<a href="https://agentmods.dev/skills/mesutgulecen/ponscli/verify"><img src="https://agentmods.dev/badge/skills/mesutgulecen/ponscli/verify/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/mesutgulecen/ponscli/verify"><img src="https://agentmods.dev/badge/skills/mesutgulecen/ponscli/verify.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.00055 | $0.00645 |
| Opus 5.5 | $0.00022 | $0.00258 |
| Sonnet 5.5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
verify 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying a change to ponscli
Four checks, in this order. Later ones are slower and depend on the earlier ones passing.
npm run typecheck
npm run lint
npm test
npm run build
Run them individually, not as one && chain: when the second fails you want the
first's output still on screen.
What each failure usually means here
typecheck: most often an ABI change. viem infers argument and return types
from the literal ABI, so adding a contract or regenerating one surfaces as a type
error at every call site that used the old shape. That is the check working.
lint: no-unnecessary-type-assertion fires a lot in this repo because the
generated ABIs are as const and already narrow. If you wrote as Address on
something coming out of addresses.ts, delete it.
npm test: the suite is offline. Every test drives the real command surface
through test/fakeChain.ts, a table of address + ABI + function → result. A test
that fails with every free endpoint failed is not a network problem: it means
the fixture is missing an answer for a call the code now makes. Add it to
answers, or to succeed if the call is a state-changing one whose arguments
the test cannot predict.
npm run build: rarely fails on its own. If it does after the others pass,
suspect a runtime-only import cycle.
The ABI gate
npm run abi:check
Fails when a committed ABI no longer matches its verified source. It is not
part of npm test on purpose: it reaches the network, and Blockscout's API is
a token bucket that a full sweep drains. Run it when you have touched
scripts/fetch-abis.mjs or suspect a redeployment, not on every change.
Before you claim something about the protocol
This project's standing rule is that protocol values come from the chain, not from contract source or from this document. The source's defaults are stale in several places that matter. If a change rests on a claim about how Pons behaves, verify it against mainnet state before writing it down:
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 · 66 lines · 55 tokens per session scan A fc0b674ab1ab
verify is a skill published in the GitHub repository mesutgulecen/ponscli (0 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 645 once invoked, about $0.0002 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-31.
Other skills, from other repositories
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
perp-cli
Multi-DEX perpetual futures trading via the perp-cli command-line tool. Use when user asks to: trade perps, check funding rates, scan/execute arbitrage (perp-perp or spot-perp), run delta-neutral strategies, bridge USDC across chains, manage positions/orders/leverage, deposit/withdraw, hedge spot+perp, trade HIP-3…
blockchain-expert
Expert-level blockchain, Web3, smart contracts, DeFi, and cryptocurrency development. Use when the user mentions Web3, smart contracts, DeFi, Ethereum, or Solidity, or when the task involves Blockchain Fundamentals, Web3 & DeFi, Smart Contract Security, or Gas Optimization.
analyzing-ethereum-smart-contract-vulnerabilities
Use when perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet. Use when performing static and symbolic analysis of solidity smart contracts using.
web3-expert
Build production-ready Web3 applications including smart contracts, dApps, DeFi protocols, and decentralized storage solutions. Use when the user mentions Web3, smart contracts or Solidity, dApps, DeFi protocols, ethers.js or web3.js, IPFS, or on-chain integration with Ethereum-compatible networks.