New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Performing Post Quantum Cryptography Migration

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards.

Apache-2.0Auto-check passedSecurity

Install Performing Post Quantum Cryptography Migration

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-post-quantum-cryptography-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills performing-post-quantum-cryptography-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performing-post-quantum-cryptography-migration .claude/skills/performing-post-quantum-cryptography-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
performing-post-quantum-cryptography-migration
GitHub stars
34k
Token cost
~3.2k tokens
SKILL.md length
935 words
Files
4 (incl. scripts, references)
Skills in repo
637
Repo updated
First seen
Licence
Apache-2.0

At a glance

Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards.

  • Works in 6 steps: Cryptographic Inventory Scanning → Crypto-Agility Assessment → Hybrid TLS Readiness Testing → …
  • Executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure
  • SKILL.md covers When to Use, Prerequisites, Core Concepts and Instructions, plus 3 more sections
  • Runs Python scripts from its folder; calls python and openssl

What it does

Performing Post Quantum Cryptography Migration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic…

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Security, covering Cryptography. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure
  • Tasks that involve Cryptography

Example prompts

  • “Use the performing-post-quantum-cryptography-migration skill to assess organizational readiness for post-quantum cryptography migration per NIST…”
  • “/performing-post-quantum-cryptography-migration”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Cryptographic Inventory Scanning
  2. Crypto-Agility Assessment
  3. Hybrid TLS Readiness Testing
  4. ML-KEM Key Encapsulation Validation
  5. ML-DSA Digital Signature Validation
  6. Migration Roadmap Generation

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • openssl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • csrc.nist.gov
    • openquantumsafe.org
    • nccoe.nist.gov
    • github.com
    • cisa.gov
    • datatracker.ietf.org
    • cyclonedx.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Performing Post Quantum Cryptography Migration loads about 3.2k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 151 tokens; SKILL.md has 935 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~151
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 935 words, ~3,178 tokens.

Download SKILL.mdSave it as .claude/skills/performing-post-quantum-cryptography-migration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
performing-post-quantum-cryptography-migration
description
Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure.
domain
cybersecurity
subdomain
cryptography
tags
post-quantum, PQC, CRYSTALS-Kyber, ML-KEM, ML-DSA, FIPS-203, FIPS-204, hybrid-TLS, crypto-agility
version
1.0
author
mukul975
license
Apache-2.0
nist_csf
PR.DS-01, PR.DS-02, PR.DS-10
mitre_attack
T1600, T1573, T1553, T1040

Performing Post-Quantum Cryptography Migration

When to Use

  • When assessing organizational readiness for the NIST post-quantum cryptography transition
  • When building a cryptographic inventory to identify quantum-vulnerable algorithms across infrastructure
  • When evaluating hybrid TLS 1.3 configurations using X25519MLKEM768 key exchange
  • When testing CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) algorithm support
  • When implementing crypto-agility to support both classical and post-quantum algorithms
  • When preparing migration roadmaps aligned with NIST IR 8547 deprecation timelines
  • When configuring oqs-provider with OpenSSL 3.x for post-quantum algorithm support

Prerequisites

  • Python 3.8+ with cryptography, requests, pyOpenSSL libraries
  • OpenSSL 3.0+ (3.5+ recommended for native ML-KEM/ML-DSA support)
  • oqs-provider for OpenSSL (for hybrid TLS testing with older OpenSSL)
  • Network access to target servers for TLS assessment
  • Administrative access for infrastructure scanning
  • Familiarity with PKI, TLS, and cryptographic protocols

Core Concepts

NIST Post-Quantum Cryptography Standards

NIST published three finalized PQC standards on August 13, 2024:

StandardAlgorithmRenamed ToPurposeBased On
FIPS 203CRYSTALS-KyberML-KEMKey Encapsulation MechanismModule lattice
FIPS 204CRYSTALS-DilithiumML-DSADigital SignaturesModule lattice
FIPS 205SPHINCS+SLH-DSADigital Signatures (backup)Stateless hash

ML-KEM (FIPS 203) -- Primary standard for key exchange and encryption. Replaces RSA and ECDH for key establishment. Three security levels: ML-KEM-512, ML-KEM-768, ML-KEM-1024.

ML-DSA (FIPS 204) -- Primary standard for digital signatures. Replaces RSA and ECDSA for signing. Three security levels: ML-DSA-44, ML-DSA-65, ML-DSA-87.

SLH-DSA (FIPS 205) -- Backup signature standard using hash-based approach. Intended as fallback if lattice-based ML-DSA is found vulnerable. Larger signatures but conservative security assumptions.

Quantum-Vulnerable Algorithms

These classical algorithms are vulnerable to quantum attack via Shor's algorithm:

AlgorithmUsageQuantum ThreatMigration Priority
RSA-2048/4096Key exchange, signatures, encryptionShor's algorithm breaks factoringCritical
ECDH (P-256, P-384)TLS key exchangeShor's algorithm breaks ECDLPCritical
ECDSACode signing, TLS certificatesShor's algorithm breaks ECDLPCritical
DSALegacy signaturesShor's algorithm breaks DLPCritical
DH (Diffie-Hellman)Key exchangeShor's algorithm breaks DLPCritical
AES-128Symmetric encryptionGrover's halves key strengthMedium (upgrade to AES-256)
SHA-256HashingGrover's reduces to 128-bitLow (still adequate)
NIST Migration Timeline (IR 8547)
  • 2024: Standards published, migration planning should begin
  • 2030: Deprecation of quantum-vulnerable algorithms for most federal systems
  • 2035: Complete removal of quantum-vulnerable algorithms from NIST standards
  • Now: "Harvest now, decrypt later" attacks make early migration essential for long-lived secrets and data requiring long-term confidentiality
Hybrid TLS Key Exchange

During the transition period, hybrid key exchange combines a classical algorithm with a post-quantum algorithm. If either algorithm is secure, the connection remains protected.

Hybrid Key Exchange: X25519MLKEM768
  = X25519 (classical ECDH) + ML-KEM-768 (post-quantum)

Client Hello:
  supported_groups: X25519MLKEM768, X25519, secp256r1
  key_share: X25519MLKEM768

Server Hello:
  selected_group: X25519MLKEM768
  key_share: X25519MLKEM768

Shared Secret = KDF(X25519_shared || MLKEM768_shared)

Instructions

Phase 1: Cryptographic Inventory Scanning

The first step in PQC migration is discovering all cryptographic algorithm usage across the enterprise. This includes TLS configurations, certificates, code libraries, key stores, and protocol configurations.

python
# Scan TLS endpoints for quantum-vulnerable algorithms
python scripts/agent.py --action scan_tls \
    --targets targets.txt \
    --output tls_inventory.json

The scanner identifies:

  • TLS protocol versions in use
  • Key exchange algorithms (RSA, ECDH, DH -- all quantum-vulnerable)
  • Certificate signature algorithms (RSA, ECDSA)
  • Cipher suite configurations
  • Certificate key sizes and expiration dates
Phase 2: Crypto-Agility Assessment

Evaluate the organization's ability to swap cryptographic algorithms without major infrastructure changes:

python
# Assess crypto-agility readiness
python scripts/agent.py --action assess_agility \
    --scan-results tls_inventory.json \
    --output agility_report.json

Key assessment areas:

  1. Protocol flexibility: Can TLS configurations be updated without downtime?
  2. Library versions: Do deployed crypto libraries support PQC algorithms?
  3. Certificate infrastructure: Can CA issue PQC certificates?
  4. Key management: Can KMS handle larger PQC key sizes?
  5. Hardware constraints: Can HSMs support PQC operations?
Phase 3: Hybrid TLS Readiness Testing

Test whether infrastructure supports hybrid key exchange with X25519MLKEM768:

python
# Test hybrid TLS support on target servers
python scripts/agent.py --action test_hybrid_tls \
    --target server.example.com:443 \
    --output hybrid_tls_report.json

OpenSSL 3.5+ (native ML-KEM support):

bash
# Test with native PQC support
openssl s_client -connect server.example.com:443 \
    -groups X25519MLKEM768

OpenSSL 3.0-3.4 with oqs-provider:

bash
# Configure oqs-provider
# /etc/ssl/openssl-oqs.cnf
[openssl_init]
providers = provider_sect

[provider_sect]
default = default_sect
oqsprovider = oqsprovider_sect

[default_sect]
activate = 1

[oqsprovider_sect]
activate = 1
module = /usr/lib/oqs-provider/oqsprovider.so

# Test hybrid TLS
OPENSSL_CONF=/etc/ssl/openssl-oqs.cnf \
openssl s_client -connect server.example.com:443 \
    -groups x25519_mlkem768

Web Server Configuration for Hybrid TLS:

Apache httpd:

apache
SSLEngine on
SSLCertificateFile /etc/ssl/certs/server.crt
SSLCertificateKeyFile /etc/ssl/private/server.key
SSLOpenSSLConfCmd Curves X25519MLKEM768:X25519:prime256v1
SSLProtocol -all +TLSv1.2 +TLSv1.3

NGINX:

nginx
ssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
Show full SKILL.md (371 more words)Show less
Phase 4: ML-KEM Key Encapsulation Validation

Validate that ML-KEM (CRYSTALS-Kyber) key encapsulation works correctly in your environment:

python
# Test ML-KEM key encapsulation at all security levels
python scripts/agent.py --action test_mlkem \
    --output mlkem_validation.json

ML-KEM parameter comparison:

ParameterML-KEM-512ML-KEM-768ML-KEM-1024
Security LevelNIST Level 1NIST Level 3NIST Level 5
Public Key Size800 bytes1,184 bytes1,568 bytes
Ciphertext Size768 bytes1,088 bytes1,568 bytes
Shared Secret32 bytes32 bytes32 bytes
Comparable ToAES-128AES-192AES-256
Phase 5: ML-DSA Digital Signature Validation

Validate ML-DSA (CRYSTALS-Dilithium) signature operations:

python
# Test ML-DSA digital signatures
python scripts/agent.py --action test_mldsa \
    --output mldsa_validation.json

ML-DSA parameter comparison:

ParameterML-DSA-44ML-DSA-65ML-DSA-87
Security LevelNIST Level 2NIST Level 3NIST Level 5
Public Key Size1,312 bytes1,952 bytes2,592 bytes
Signature Size2,420 bytes3,293 bytes4,595 bytes
Secret Key Size2,560 bytes4,032 bytes4,896 bytes
Phase 6: Migration Roadmap Generation

Generate a prioritized migration roadmap based on inventory and assessment results:

python
# Generate complete migration roadmap
python scripts/agent.py --action roadmap \
    --scan-results tls_inventory.json \
    --agility-results agility_report.json \
    --output migration_roadmap.json

The roadmap prioritizes systems by:

  1. Data sensitivity: Systems handling long-lived secrets migrate first
  2. Exposure level: Internet-facing services before internal
  3. Crypto-agility: Systems that can easily swap algorithms first
  4. Compliance requirements: Federal/regulated systems per NIST IR 8547 timeline
  5. Dependency chains: Libraries and frameworks before applications

Examples

Full Assessment Pipeline
bash
# Step 1: Scan all TLS endpoints
python scripts/agent.py --action scan_tls --targets hosts.txt --output scan.json

# Step 2: Assess crypto-agility
python scripts/agent.py --action assess_agility --scan-results scan.json --output agility.json

# Step 3: Test hybrid TLS on critical servers
python scripts/agent.py --action test_hybrid_tls --target critical.example.com:443

# Step 4: Validate ML-KEM support
python scripts/agent.py --action test_mlkem --output mlkem.json

# Step 5: Validate ML-DSA support
python scripts/agent.py --action test_mldsa --output mldsa.json

# Step 6: Generate migration roadmap
python scripts/agent.py --action roadmap --scan-results scan.json --agility-results agility.json --output roadmap.json
Quick Server Assessment
bash
# Single server PQC readiness check
python scripts/agent.py --action scan_tls --target server.example.com:443

Validation Checklist

  • Cryptographic inventory covers all TLS endpoints, certificates, and key stores
  • All quantum-vulnerable algorithms (RSA, ECDH, ECDSA, DH, DSA) are identified
  • Crypto-agility assessment documents library versions and upgrade paths
  • Hybrid TLS (X25519MLKEM768) tested on representative server configurations
  • ML-KEM key encapsulation validated at target security level (768 recommended)
  • ML-DSA signature verification validated for certificate chain use
  • SLH-DSA (FIPS 205) evaluated as backup signature algorithm
  • Migration roadmap prioritizes by data sensitivity and compliance timeline
  • OpenSSL version and oqs-provider compatibility confirmed
  • Key size increases accounted for in network and storage capacity planning
  • HSM/KMS compatibility with PQC algorithms verified
  • Performance impact of PQC algorithms benchmarked under production load
  • "Harvest now, decrypt later" risk assessed for sensitive data channels
  • Certificate Authority PQC readiness confirmed for certificate issuance

References

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/performing-post-quantum-cryptography-migration of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Performing Post Quantum Cryptography Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Performing Post Quantum Cryptography Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Performing Post Quantum Cryptography Migration this skillmukul975/Anthropic-Cybersecurity-Skills34k—~3.2kAutomated safety check: PassApache-2.0
Bom Explorecdxgen/cdxgen1.1k—~1.2kAutomated safety check: PassApache-2.0
Webcrypt MCPputervision/state-memory-mcp111—~847Automated safety check: PassMIT
Security Reviewvalory-xyz/open-autonomy129—~11kAutomated safety check: NotesApache-2.0
Hashcat Password Recovery WorkflowAgentSecOps/SecOpsAgentKit2201 repos~3.3kAutomated safety check: NotesCustom licence
Altllm Portal Authinternet-court/internet-court-skill6.4k1 repos~632Automated safety check: PassISC

Similar skills

  • Bom Explore

    cdxgen/cdxgen

    Explores and triages a CycloneDX BOM interactively with the cdxi REPL, using built-in commands for dependency trees, licenses, services, cryptographic assets, audit findings, evidence occurrences…

    1.1k GitHub stars~1.2k tokensUpdated today
    SecurityAuto-check passed

  • Webcrypt MCP

    putervision/state-memory-mcp

    Teaches the agent to use the WebCrypt MCP server for AES-256-GCM symmetric encryption, RSA-4096 hybrid encryption, key generation, digital signatures, hashing, and post-quantum cryptography.

    111 GitHub stars~847 tokensUpdated 5 days ago
    SecurityAuto-check passed

  • Security Review

    valory-xyz/open-autonomy

    Security review of an open-autonomy agent service — cryptographic key handling, dynamic code execution, ABCI authentication and replay, secret exposure, dependency supply chain, and deployment…

    129 GitHub stars~11k tokensUpdated 24 days ago
    SecurityAuto-check: notes

  • Hashcat Password Recovery Workflow

    AgentSecOps/SecOpsAgentKit

    Guides authorized password-hash recovery with hashcat for security audits, forensic cases and policy testing, starting with an explicit authorization check before any cracking runs.

    220 GitHub starsUsed in 1 repo~3.3k tokens
    SecurityAuto-check: notes

  • Altllm Portal Auth

    internet-court/internet-court-skill

    A skill your agent uses when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login…

    6.4k GitHub starsUsed in 1 repo~632 tokens
    SecurityAuto-check passed

  • Crypto Analysis

    hypnguyen1209/offensive-claude

    A skill your agent uses when assessing cryptography — TLS/PKI auditing, RSA/ECC key attacks, ECDSA nonce lattice recovery, symmetric/AEAD misuse, JWT/JOSE forgery, hash cracking, post-quantum…

    386 GitHub stars~2.2k tokensUpdated 10 days ago
    SecurityAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 637 skills in this repo

  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Performing Post Quantum Cryptography Migration

What does Performing Post Quantum Cryptography Migration do?

Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards. Performing Post Quantum Cryptography Migration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards.

When should I use Performing Post Quantum Cryptography Migration?

Performing Post Quantum Cryptography Migration fits situations like: executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure; tasks that involve Cryptography.

How do I install Performing Post Quantum Cryptography Migration in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-post-quantum-cryptography-migration -a claude-code`. Or copy the skill folder (skills/performing-post-quantum-cryptography-migration in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/performing-post-quantum-cryptography-migration in your project. Claude Code loads it when a task matches its description.

How do I install Performing Post Quantum Cryptography Migration in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-post-quantum-cryptography-migration -a codex`. Or copy the skill folder (skills/performing-post-quantum-cryptography-migration in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/performing-post-quantum-cryptography-migration in your project. Codex loads it when a task matches its description.

Can I use Performing Post Quantum Cryptography Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-post-quantum-cryptography-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performing-post-quantum-cryptography-migration, .gemini/skills/performing-post-quantum-cryptography-migration, .github/skills/performing-post-quantum-cryptography-migration and .opencode/skills/performing-post-quantum-cryptography-migration in your project.

What does Performing Post Quantum Cryptography Migration need to run?

Going by SKILL.md and its folder, Performing Post Quantum Cryptography Migration needs Python for the scripts in its folder and the command-line tools its instructions call (python and openssl). Our summary lists: Python 3.

Does Performing Post Quantum Cryptography Migration access the network?

SKILL.md names 7 domains. As links in the text: csrc.nist.gov, openquantumsafe.org, nccoe.nist.gov, github.com, cisa.gov, datatracker.ietf.org and cyclonedx.org. This is read from the text; nothing was executed.

Is Performing Post Quantum Cryptography Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Performing Post Quantum Cryptography Migration use?

Performing Post Quantum Cryptography Migration is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Performing Post Quantum Cryptography Migration use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Performing Post Quantum Cryptography Migration?

Skills that share tags, products or a category with Performing Post Quantum Cryptography Migration: Bom Explore (cdxgen/cdxgen, 1.1k stars), Webcrypt MCP (putervision/state-memory-mcp, 111 stars), Security Review (valory-xyz/open-autonomy, 129 stars) and Hashcat Password Recovery Workflow (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Performing Post Quantum Cryptography Migration?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 33,922 GitHub stars. The repository holds 637 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.