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 agentmods add skills/putervision/webcrypt/webcrypt-mcpnpx skills add putervision/WebCrypt --skill webcrypt-mcpgit clone --depth 1 https://github.com/putervision/WebCryptWhat 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 | $0.00058 | $0.01070 |
| Opus 5 | $0.00029 | $0.00535 |
| Sonnet 5 | $0.00012 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
webcrypt-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cryptographic Memory & Vault Tooling (webcrypt-mcp)
This project provides webcrypt-mcp, a native Model Context Protocol server for zero-dependency AES-256-GCM encryption, RSA-4096 hybrid public-key encryption, digital signatures, cryptographic hashes, and post-quantum cryptography.
1. Mandatory Workflow & Priority
- Confidential Artifacts: Whenever saving sensitive credentials, tokens, or private workflow states, encrypt them using
encrypt_payload(mode: "data", password: "...")orencrypt_payload(mode: "symmetric", password: "..."). - Key Management: Use
manage_keys(action: "generate", type: "rsa" | "ecdh" | "ecdsa" | "rsa-pss" | "hmac")to generate cryptographically strong JWK-formatted keys for inter-agent communication. - Integrity & Signatures: Before completing tasks that produce verifiable evidence (such as evidence packs or release binaries), compute signatures or HMAC tags using
sign_verify(action: "sign", algorithm: "ECDSA" | "HMAC"). - Triple Memory Triad:
state-memory-mcp: Workflow state tracking.vision-memory-mcp: Visual state caching.webcrypt-mcp: Encryption of sensitive DAG nodes, visual cache database vaults, and signature verification.
2. Complete Tool Reference
| Tool Name | Key Inputs | Description |
|---|---|---|
encrypt_payload |
mode ('symmetric' | 'asymmetric' | 'data'), data, password?, public_key_jwk? |
Encrypt plaintext, JSON object, or binary data. |
decrypt_payload |
mode ('symmetric' | 'asymmetric' | 'data'), ciphertext, password?, private_key_jwk? |
Decrypt ciphertext back to plaintext or structured JSON. |
manage_keys |
action ('generate' | 'generate_random_password'), type ('rsa' | 'ecdh' | 'ecdsa' | 'rsa-pss' | 'hmac'), modulusLength?, namedCurve?, length? |
Generate cryptographic keys (JWK format) or secure random passwords. |
crypto_hash |
algorithm ('SHA-256' | 'SHA-384' | 'SHA-512' | 'SHA3-256' | 'SHA3-512'), data, encoding ('hex' | 'base64') |
Compute cryptographic hash digests. |
sign_verify |
action ('sign' | 'verify'), algorithm ('ECDSA' | 'RSA-PSS' | 'HMAC' | 'HMAC-SHA3'), data, signature?, password?, key_jwk? |
Sign or verify messages with ECDSA, RSA-PSS, or HMAC. |
pqc_kem_sign |
action ('generate_kyber_keypair' | 'kyber_encapsulate' | 'kyber_decapsulate' | 'hybrid_encapsulate' | 'hybrid_decapsulate' | 'generate_dilithium_keypair' | 'dilithium_sign' | 'dilithium_verify'), level?, public_key_b64?, private_key_b64?, ... |
Post-quantum Kyber KEM, Dilithium signatures, and Hybrid KEM. |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 49 lines · 58 tokens per session scan A 6e091f5bd787
webcrypt-mcp is a skill published in the GitHub repository putervision/WebCrypt (24 stars, last pushed 11d ago), licensed MIT. It adds 58 tokens to every session and 1,070 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-08-30.
Other skills, from other repositories
Cryptographic Analysis & Assessment
SSL/TLS auditing, cipher suite analysis, hash algorithm identification, encryption implementation review, and cryptographic weakness detection in code.
analyzing-ransomware-encryption-behavior
Analyzes how a ransomware sample encrypts files: identifying the crypto scheme (symmetric/asymmetric/hybrid), key handling, file targeting and extension/marker changes, shadow-copy deletion, and ransom-note artifacts. Activates for requests to analyze ransomware encryption, assess decryptability, or study ransomware…
covalent-bond-test
How to write, run, and debug tests for Covalent Bond: the runner, the in-process mock relay, deterministic polling, port allocation, cleanup conventions, and what every kind of change must cover. Use when adding or modifying a test, when a suite fails, or before committing any behavior change.
covalent-bond-run
How to run Covalent Bond on a machine and pair two AI agents, covering how to register the MCP server, start a relay (mock or deployed), create/join a session, send files, and troubleshoot. Use when a user wants to set up, start, connect, or test Covalent Bond, or asks why a session won't connect.
covalent-bond-self-relay
Deploy the user's own Covalent Bond relay to their Cloudflare account: install wrangler, walk them through the browser login, run the deploy, verify /health, and set COVALENTRELAYURL. Use when a user asks to set up, deploy, or host their own relay instead of using the public one.
covalent-bond-guardrails
Guardrails for any agent editing the Covalent Bond repository, covering the security invariants that must never be broken, what code NOT to add, and the verify-don't-guess working discipline. Use whenever writing or changing code, tests, or config in this repo before making the edit.