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 lidonation/Cardano-mcp --skill aiken-verifygit clone --depth 1 https://github.com/lidonation/Cardano-mcpWrote 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/lidonation/cardano-mcp/aiken-verify)<a href="https://agentmods.dev/skills/lidonation/cardano-mcp/aiken-verify"><img src="https://agentmods.dev/badge/skills/lidonation/cardano-mcp/aiken-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/lidonation/cardano-mcp/aiken-verify"><img src="https://agentmods.dev/badge/skills/lidonation/cardano-mcp/aiken-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.00063 | $0.00599 |
| Opus 5 | $0.00032 | $0.00300 |
| Sonnet 5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
aiken-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 today.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aiken verify-before-trust
Aiken is a strict, statically-typed language for Cardano validators. A snippet that looks right is not the same as a snippet that compiles — indentation, type signatures, and stdlib imports in Aiken are all points where confident, plausible-looking code silently fails to build. Never present Aiken code as correct without actually compiling it.
Workflow
- Write or gather the full Aiken snippet (a validator, a helper function, a test) that is about to be shown to the user.
- Call
validate_aiken_snippet(from thecardano-mcpserver bundled with this plugin) with that exact snippet. It shells out to the realaiken buildcompiler in a temporary project and returns actual compiler output — not a guess. - Check the returned
statusfield — it's one of three states, not two:"ok"— compiled cleanly. Say so plainly ("compiles cleanly againstaiken build") before presenting the code."error"— a real compile failure. Read the compiler's error output, fix the code, and validate again before showing anything to the user. Do not show a failing snippet as if it were final."unavailable"— theaikenCLI itself wasn't found in this environment; the code was not checked at all. Do not treat this the same as a passing or failing compile — say explicitly that verification couldn't run and the code is unverified, then fall back to your best understanding of Aiken syntax, clearly flagged as such.
- If the
cardano-mcpMCP server isn't available in this session at all (the tool call fails outright rather than returning anunavailablestatus), say so explicitly and fall back the same way. Never imply a snippet was compiled when it wasn't.
Why this exists
Generic LLM-written Aiken is frequently wrong in small, confident-looking
ways — a missing use aiken/builtin, a validator returning Bool where a
True/False-shaped constructor is expected, or a datum shape mismatch that
only shows up as a compile error. A verification step against the real
compiler beats a model's confidence about whether code is correct, every
time.
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.
- today First seen · 46 lines · 63 tokens per session scan A 3fa1f7751263
aiken-verify is a skill published in the GitHub repository lidonation/Cardano-mcp (2 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 599 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-09-21.
Other skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
web3-poc-foundry
Complete Foundry PoC writing guide + all cheatcodes + DeFiHackLabs reproduction patterns. Use this when building a proof of concept exploit, setting up a fork test, using Foundry cheatcodes, or reproducing a known DeFi hack for learning.
tevm
Build, simulate, test, fork, and debug EVM transactions in TypeScript with tevm 1.0.0-rc.151. Use for in-process EVM scripts, typed Solidity imports, lazy mainnet or OP-stack forks, direct account and storage setup, viem-compatible contract actions, Vitest EVM tests, traces, and transaction simulation.
smart-contract-testing
Guide for testing smart contracts using Foundry and Hardhat, covering unit tests, fuzz testing, invariant testing, fork testing, and gas benchmarking.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.