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 skills add Fulcrum-Enterprises/verify-proof --skill verifygit clone --depth 1 https://github.com/Fulcrum-Enterprises/verify-proofWrote 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/fulcrum-enterprises/verify-proof/verify)<a href="https://agentmods.dev/skills/fulcrum-enterprises/verify-proof/verify"><img src="https://agentmods.dev/badge/skills/fulcrum-enterprises/verify-proof/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/fulcrum-enterprises/verify-proof/verify"><img src="https://agentmods.dev/badge/skills/fulcrum-enterprises/verify-proof/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.00059 | $0.00337 |
| Opus 5.5 | $0.00024 | $0.00135 |
| Sonnet 5.5 | $0.00012 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
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 2d 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.
What it actually says
Verify a file against its proof
Use the verify-proof MCP tools. Verification is pure computation on this machine: nothing is sent anywhere and no account is needed.
Steps
- Get the path of the file and of its proof JSON (often
<file name>.proof.jsonnext to the file). If the user only has a hash, useverify_hashwith the hash and the proof JSON instead. - Call
verify_filewithfile_pathandproof_path. - If it verifies, report the chain, the transaction id and the anchor time, and give the block explorer link so the user can see the transaction themselves (for Polygon:
https://polygonscan.com/tx/<transaction id>). - If it fails, say which check failed. A hash mismatch means this is not the anchored file: it was changed, even by one byte, or it is a different file.
- If the user wants to know what the proof means, call
explain_proofwith the proof JSON and relay it in plain words.
What a proof shows
- That a file with this exact SHA-256 fingerprint existed by the anchor time, and has not changed since.
- Not who made the file, not that its contents are true, and not a copyright registration.
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.
- 2d ago First seen · 22 lines · 59 tokens per session scan A 366069999fbe
verify is a skill published in the GitHub repository Fulcrum-Enterprises/verify-proof (0 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 337 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-10-17.
Other skills, from other repositories
blockchain-cryptography
Use this skill when asked about cryptographic primitives in blockchain, elliptic curve cryptography, hash functions, Merkle trees, digital signatures, zero-knowledge proofs, key derivation, BIP standards, and blockchain-specific crypto implementations. Languages: C++, Rust, Go, Python. Covers secp256k1, BN254…
blockchain-core
Use this skill when asked about blockchain fundamentals, consensus mechanisms, PoW, PoS, gas, staking, blockchain data structures, DAG consensus, Avalanche, MEV, PBS, economic security, blockchain node implementation. Languages: C++, Go. Covers core protocol engineering including consensus algorithms (Nakamoto, PBFT…
stablecoin-chain-explorer
Explore stablecoin TVL distribution and yield opportunities by blockchain. Query which chains have the most stablecoins, compare cross-chain yields, and find the best opportunities on Ethereum, BSC, Arbitrum, Base, Polygon, and more. Also for protocols and issuers researching where stablecoin TVL and liquidity…
tokenomist-fundraising-lookup
Look up fundraising rounds, investors, and valuation data for tokens. Use when finding who invested, at what valuation, or analyzing investor portfolios.
tokenomist-unlock-analysis
Analyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns. Use when checking unlock impact on market cap or reviewing unlock schedules.
tokenomist-allocation-breakdown
Get the full allocation distribution for a token — who owns what and how much is locked vs unlocked. Use when analyzing supply distribution across team, investors, community, etc.