mint-cert

mint-cert is a command for coding agents from omermaksutii/RugProof. It costs 22 tokens per session (886 once invoked), scanned A, original, MIT.

A command for creating a soulbound audit certificate NFT on Berachain or another supported blockchain. The certificate records a completed audit, with its report bundle pinned to IPFS, a network for storing files.

In plain words
What is it for?
Use it after an audit to bundle the results, pin the files to IPFS, and mint the certificate NFT using a configured contract and wallet.
Why use it?
It gives a completed audit a blockchain record that can be linked to its audit files and issuer signature.

Command

Part of the rugproof plugin — 35 commands, 23 agents shipped together

Install

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.

agentmods
npx agentmods add commands/omermaksutii/rugproof/mint-cert
Clone the repo
git clone --depth 1 https://github.com/omermaksutii/RugProof

Or install rugproof, the plugin that ships this one along with the rest of its 35 commands, 23 agents.

Wrote 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.

agentmods badge for mint-cert

README.md
[![agentmods](https://agentmods.dev/badge/commands/omermaksutii/rugproof/mint-cert.svg)](https://agentmods.dev/commands/omermaksutii/rugproof/mint-cert)
Your own site
<a href="https://agentmods.dev/commands/omermaksutii/rugproof/mint-cert"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/mint-cert.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 886 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00886
Opus 5 $0.00011 $0.00443
Sonnet 5 $0.00004 $0.00177
Haiku 4.5 $0.00002 $0.00089

Measured 4d ago against content hash 478c7d0cef4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mint-cert scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST https://api.omermaksutii.github.io/RugProof/v1/issue-cert \
commands/mint-cert.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/mint-cert — mint an Audit Certificate NFT

Mints a soulbound NFT recording the completed audit. The token's metadata bundle (audit JSON + Markdown report + PNG card) is pinned to IPFS.

Default chain: Berachain (the launch ecosystem).

Prerequisites

  • A completed /audit (with results saved to rugproof-reports/)
  • A deployed AuditCertificate contract — see nft/DEPLOY.md for the Berachain runbook. Record its address in .rugproof.yml:
    certificate:
      chain_id: 80094            # Berachain mainnet (Bepolia testnet: 80069)
      address: "0xDeployedCertAddress"
    
  • Wallet env: RUGPROOF_SUBJECT_PK (the subject's signing key) and RUGPROOF_SUBJECT_ADDR
  • An issuer signature: produce it locally with the bundled signer (no backend needed) — node scripts/dist/sign-cert.js --chain-id <id> --cert-address <addr> --subject <user> --report-hash <0x…> --ipfs-cid <Qm…> --target-name <name> --grade <0-6> --signer-key $RUGPROOF_ISSUER_KEY. Its signerAddress must match the contract's configured issuer.
  • IPFS pinning credentials (Pinata / Web3.Storage / Filecoin) if using --ipfs-pin

Procedure

  1. Bundle the audit. Collect:

    • findings.json
    • audit.md rendered report
    • audit-card.png PNG card Hash all three together → reportHash (sha256).
  2. Pin to IPFS. If --ipfs-pin, upload the bundle. Capture CID. Otherwise expect RUGPROOF_BUNDLE_CID env var.

  3. Request issuer signature. POST the bundle metadata + reportHash to Rugproof's signer:

    curl -X POST https://api.omermaksutii.github.io/RugProof/v1/issue-cert \
         -H "content-type: application/json" \
         -d '{ "subject": "0x...", "reportHash": "0x...", "ipfsCid": "Qm...", "targetName": "MyVault", "grade": 5, "chainId": 80094 }'
    

    Returns { "issuerSig": "0x..." }.

  4. Submit the mint tx. Call AuditCertificate.issue(subject, reportHash, ipfsCid, targetName, grade, issuerSig) on the deployment for the target chain.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 4d ago First seen · 73 lines · 22 tokens per session scan A 478c7d0cef4f

Subscribe to this mod's changes

mint-cert is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 886 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.