Cougr: Skill for Claude Code

.claude/skills/zk-proofs/SKILL.md

zk-proofs is a skill for Claude Code from salazarsebas/Cougr. It costs 100 tokens per session (1,432 once invoked), scanned A, original, MIT.

A guide to zero-knowledge cryptography and privacy features for Stellar and Soroban, Stellar’s smart-contract platform. It covers proof checking, private assets, privacy pools, and commitment trees, while noting that support depends on protocol and software versions.

In plain words
What is it for?
Use it when building Soroban contracts that check zero-knowledge proofs, or when integrating Noir or RISC Zero proofs. It also covers privacy pools, confidential tokens, and Merkle-tree commitments.
Why use it?
It helps developers avoid relying on cryptography that their target network or SDK does not yet support. It also points out where to check feature status and plan fallback paths.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is salazarsebas/Cougr's own configuration. It tells Claude Code how to work on Cougr itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Cougr configures →

Reuse

Borrowing it

Nothing to install: this file belongs to salazarsebas/Cougr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/salazarsebas/Cougr/main/.claude/skills/zk-proofs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/salazarsebas/Cougr

Made for: Claude Code.

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 zk-proofs

README.md
[![agentmods](https://agentmods.dev/badge/skills/salazarsebas/cougr/zk-proofs/github.svg)](https://agentmods.dev/skills/salazarsebas/cougr/zk-proofs)
Your own site
<a href="https://agentmods.dev/skills/salazarsebas/cougr/zk-proofs"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/zk-proofs/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.

agentmods 80×15 button for zk-proofs

Your own site · 80×15
<a href="https://agentmods.dev/skills/salazarsebas/cougr/zk-proofs"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/zk-proofs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,432 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00100 $0.01432
Opus 5.5 $0.00040 $0.00573
Sonnet 5.5 $0.00020 $0.00286
Haiku 4.5 $0.00010 $0.00143

Measured today against content hash ae4e1b2a2f28, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zk-proofs 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.

.claude/skills/zk-proofs/SKILL.md · 168 lines

How it starts

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

Zero-Knowledge Proofs & Privacy

Privacy patterns and ZK verification on Stellar/Soroban. Capability is protocol- and SDK-version dependent - always verify CAP status, network version, and soroban-sdk host-function support before relying on a primitive.

When to use this skill

  • Implementing a Groth16 (or other SNARK) verifier as a Soroban contract
  • Using BLS12-381 host functions
  • Planning for BN254 / Poseidon (currently proposed via CAP-0074/0075)
  • Integrating Noir or RISC Zero proofs
  • Building privacy pools, confidential tokens, or Merkle-tree-backed commitments

Status-sensitive - always verify

  1. CAP status (Accepted/Implemented vs draft)
  2. Target network software + protocol version
  3. soroban-sdk release support for the target host functions
  4. Available feature flags + graceful fallback paths
  • Soroban verifier contract patterns + tests → ../soroban/SKILL.md
  • Confidential-token integration with classic assets → ../assets/SKILL.md
  • Off-chain proof verification UI → ../dapp/SKILL.md
  • CAPs referenced here → ../standards/SKILL.md

When to use this guide

Use this guide when the user asks for:

  • On-chain ZK proof verification patterns
  • Privacy-preserving smart contract architecture
  • BN254/Poseidon readiness planning
  • Groth16 or PLONK integration strategy
  • Cross-chain proof verification design

This guide is intentionally status-aware. ZK capabilities on Stellar evolve with protocol and SDK releases.

Source-of-truth checks (required)

Before implementation, always verify:

  1. CAP status in stellar/stellar-protocol (Accepted/Implemented vs draft/awaiting decision)
  2. Target network protocol/software version
  3. soroban-sdk support for required cryptographic host functions
  4. Availability of production examples matching your proving system

Primary references:

Read the full file on GitHub · 168 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. today First seen · 168 lines · 100 tokens per session scan A ae4e1b2a2f28

Subscribe to this mod's changes

zk-proofs is a skill published in the GitHub repository salazarsebas/Cougr (53 stars, last pushed 17d ago), licensed MIT. It adds 100 tokens to every session and 1,432 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-11-07.

Related

zk-proofs compared with skills from other repositories

zk-proofs next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
zk-proofssalazarsebas/CougrSkill5317d agoMITA100Claude Code
frontend-designrylsherdamz-rgb/stellar-forgeSkill175d agoMITA51Claude Code
stellar-forgerylsherdamz-rgb/stellar-forgeSkill175d agoMITA82Claude Code
smart-contractsrylsherdamz-rgb/stellar-forgeSkill175d agoMITA44Claude Code
dapprylsherdamz-rgb/stellar-forgeSkill175d agoMITA48Claude Code
stellar-mcprylsherdamz-rgb/stellar-forgeSkill175d agoMITA61Claude Code
datarylsherdamz-rgb/stellar-forgeSkill175d agoMITA41Claude Code