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 skills add m3taz-ahmed/ai-globals --skill post-quantum-lordgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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.
[](https://agentmods.dev/skills/m3taz-ahmed/ai-globals/post-quantum-lord)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/post-quantum-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/post-quantum-lord/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.
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/post-quantum-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/post-quantum-lord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.01274 |
| Opus 5 | $0.00028 | $0.00637 |
| Sonnet 5 | $0.00011 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
post-quantum-lord 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Quantum Cryptography Lord
[OBJ] Migrate systems to post-quantum cryptography (PQC) using NIST-standardized algorithms (FIPS 203/204/205) and hybrid schemes.
Problem
Quantum computers will break RSA, ECDSA, and ECDH. NIST standardized PQC algorithms (Aug 2024): ML-KEM (Kyber, FIPS 203), ML-DSA (Dilithium, FIPS 204), SLH-DSA (SPHINCS+, FIPS 205). Go 1.27, Rust, OpenSSL 3.5+ now ship PQC primitives. Migration is a multi-year effort — start now with hybrid schemes.
Rules
- [REQ] Know the NIST PQC standards:
- ML-KEM (FIPS 203) — Key Encapsulation Mechanism (replaces ECDH for key exchange)
- ML-DSA (FIPS 204) — Digital Signature Algorithm (replaces RSA/ECDSA)
- SLH-DSA (FIPS 205) — Hash-based signatures (slow but conservative, fallback)
- [REQ] Use hybrid schemes during migration. Combine classical (X25519/Ed25519) + PQC (ML-KEM-768/ML-DSA-65) for transition period.
X25519Kyber768Draft00for TLS,Ed25519+ML-DSA-65for signatures. - [REQ] Use
crypto/mldsain Go 1.27+ for ML-DSA signatures:mldsa.GenerateKey(),mldsa.Sign(),mldsa.Verify(). Prefer over hand-rolled PQC. - [REQ] Use OpenSSL 3.5+ for PQC in C/C++/Python:
EVP_PKEY_CTX_new_from_name(NULL, "ML-KEM-768", NULL). - [REQ] TLS 1.3 + PQC hybrid. Use
SSL_CTX_set1_groups_listwithX25519Kyber768Draft00(orMLKEM768) for post-quantum TLS. Supported in OpenSSL 3.5+, BoringSSL, AWS s2n. - [REQ] Larger key/signature sizes. ML-DSA-65: pk=1952B, sig=3293B (vs Ed25519: pk=32B, sig=64B). Plan storage, bandwidth, database schema changes.
- [REQ] Crypto-agility. Abstract crypto behind interfaces so algorithms can be swapped without code changes.
KeyAlgorithmenum,SignatureSchemeenum. - [REQ] Inventory crypto assets. Identify all RSA, ECDSA, ECDH usage: TLS certs, JWT signing, code signing, SSH, VPN, database encryption, backups.
- [REQ] Prioritize by exposure. Long-lived secrets (TLS certs, code signing) first — these are harvest-now-decrypt-later targets. Short-lived tokens last.
- [REQ] Test PQC interop. Use
OQS OpenSSLprovider orPQC-Nettest vectors. Verify cross-implementation compatibility. - [REQ] HSM support. Verify HSMs support PQC algorithms before migration. Most HSMs (YubiHSM, Thales, Utimaco) added ML-DSA/ML-KEM in 2025-2026 firmware.
- [PROHIBIT] Never roll your own PQC implementation — use stdlib (Go
crypto/mldsa), OpenSSL, liboqs, or BoringSSL. - [PROHIBIT] Never use pure PQC without hybrid during transition — classical fallback needed for crypto-agility.
- [PROHIBIT] Never assume PQC is quantum-resistant forever — monitor for cryptanalysis breakthroughs.
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.
- 3d ago First seen · 76 lines · 56 tokens per session scan A 5c3a767b07ab
post-quantum-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,274 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-09-09.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…