Works with the AI Agents you already use
pq Signature
Post-quantum signatures (ML-DSA-87, NIST FIPS 204) for AI agents. Sign and verify in-memory. Zero network calls. NIST Level 5.
Free
pq-signature
Example session with this skill installed
Sign the message "deploy-production-v1" with ML-DSA-87 and verify it. Also prove that a tampered message is rejected.
- Read your context and instructions
- Compiled the pq-signature
Summary
Generated an ML-DSA-87 keypair, signed the message deploy-production-v1, verified it successfully, and proved that a tampered message is rejected. All operations ran in-memory with zero network calls.
$ node examples/demo.mjs
Keygen: 86 ms
Public key size: 2592 bytes
Private key size: 4896 bytes
Sign: 84 ms
Signature size: 4627 bytes
Verify: 24 ms
Valid: true ← ✅ signature matches
Tampered: false ← ✅ tampering rejected
Signature
| Field | Value |
|---|---|
| Message | deploy-production-v1 |
| Algorithm | ML-DSA-87 (NIST FIPS 204) |
| Public key | 2592 bytes |
| Private key | 4896 bytes |
| Signature | 4627 bytes |
| Sign time | 84 ms |
| Verify time | 24 ms |
Tamper check
| Test | Expected | Actual |
|---|---|---|
| Original message | valid | ✅ true |
Message + x (tampered) | invalid | ✅ false |
| Different public key | invalid | ✅ false |
Security guarantees
- 🔒 No network calls during sign or verify
- 🔒 No keys persisted to disk
- 🔒 No file system access
- 🔒 All operations in-memory
- 🔒 Uses audited
@noble/post-quantum@0.4.0
Next steps
- Store the private key in your own secret manager (the skill never persists it).
- Distribute the public key to verifiers.
- Re-run
verifyanytime to check the signature offline. - For long-lived attestations, ML-DSA-87 is the right choice (NIST Level 5).
Connects securely to your tools. The creator never sees your data.
About this skill
██████╗ ██████╗ ███████╗██╗ ██████╗ ███╗ ██╗
██╔══██╗██╔═══██╗ ██╔════╝██║██╔════╝ ████╗ ██║
██████╔╝██║ ██║█████╗███████╗██║██║ ███╗██╔██╗ ██║
██╔═══╝ ██║▄▄ ██║╚════╝╚════██║██║██║ ██║██║╚██╗██║
██║ ╚██████╔╝ ███████║██║╚██████╔╝██║ ╚████║
╚═╝ ╚══▀▀═╝ ╚══════╝╚═╝ ╚═════╝ ╚═╝ ╚═══╝
ML-DSA-87 · NIST FIPS 204 · NIST Level 5 · Zero Network Calls
What it does
Post-quantum digital signatures via ML-DSA-87 (formerly Dilithium5), standardized by NIST as FIPS 204 in August 2024. Quantum computers will eventually break RSA and ECDSA. ML-DSA-87 is what replaces them.
┌──────────────────────────────────────────────────────────┐
│ │
│ message ──┐ │
│ ▼ │
│ ┌─────────┐ ┌──────────────┐ │
│ │ sign │─────▶│ signature │ 4627 bytes │
│ └─────────┘ └──────────────┘ │
│ ▲ │ │
│ │ ▼ │
│ private key ┌─────────┐ │
│ 4896 bytes │ verify │──▶ ✅ valid │
│ └─────────┘ ❌ tampered │
│ ▲ │
│ │ │
│ public key │
│ 2592 bytes │
└──────────────────────────────────────────────────────────┘
Specs at a glance
| Property | Value |
|---|---|
| Algorithm | ML-DSA-87 (Dilithium5) |
| Standard | NIST FIPS 204 |
| Security level | NIST Level 5 |
| Public key | 2592 bytes |
| Private key | 4896 bytes |
| Signature | 4627 bytes |
| Sign time | ~4 ms (ARM64) |
| Verify time | ~2 ms (ARM64) |
| Network calls | 0 |
| Native binaries | 0 |
| Bundle size | ~50 KB |
When to use it
✅ Long-lived credentials that must survive the quantum transition
✅ Offline signature verification
✅ High-assurance attestations (NIST Level 5)
✅ Tamper-proof evidence for AI agent workflows
✅ Zero-trust systems with no network dependencies
See it work
$ node examples/demo.mjs
Keygen: 86 ms
Public key size: 2592 bytes
Private key size: 4896 bytes
Sign: 84 ms
Signature size: 4627 bytes
Verify: 24 ms
Valid: true ← ✅ signature matches
Tampered: false ← ✅ tampering rejected
Why buy it
| Reason | Detail |
|---|---|
| NIST standard | The algorithm the U.S. government picked for post-quantum signatures |
| Audited dependency | Built on @noble/post-quantum@0.4.0 (Trail of Bits audit) |
| Zero network | Runs entirely in-memory. No RPC, no telemetry, no hidden endpoints |
| Portable | ARM64, x86_64, Termux, Docker, macOS, Linux. No native binaries |
| Fast | Sign in ~4 ms, verify in ~2 ms on mobile hardware |
| Stateless | Never stores keys. You provide them per call |
Security model
🔒 No key storage
🔒 No network calls
🔒 No file system access
🔒 Keys provided per invocation
🔒 Runs entirely in-memory
🔒 Public audit of the underlying library
Standards & references
- NIST FIPS 204 — ML-DSA (Module-Lattice Digital Signature Algorithm)
- NIST Level 5 — highest security category
- @noble/post-quantum 0.4.0 — audited by Trail of Bits
- Former name — Dilithium5 (renamed at standardization)
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
This skill does not include persistent key storage, key rotation, or key recovery. Users must manage private keys themselves via their own secret manager. It does not sign files on disk — it signs UTF-8 strings passed as arguments. It does not include a CLI wrapper for batch operations. It does not support ML-KEM, ML-DSA-44, or ML-DSA-65 — only ML-DSA-87 (NIST Level 5).
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 20 days ago
- Free with an Agensi account
- Software
Node.js 18+