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 xalgorix/xalgorix --skill implementing-rsa-key-pair-managementgit clone --depth 1 https://github.com/xalgorix/xalgorixWrote 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/xalgorix/xalgorix/implementing-rsa-key-pair-management)<a href="https://agentmods.dev/skills/xalgorix/xalgorix/implementing-rsa-key-pair-management"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/implementing-rsa-key-pair-management/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/xalgorix/xalgorix/implementing-rsa-key-pair-management"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/implementing-rsa-key-pair-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01150 |
| Opus 5 | $0.00025 | $0.00575 |
| Sonnet 5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
implementing-rsa-key-pair-management 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementing RSA Key Pair Management
Overview
RSA (Rivest-Shamir-Adleman) is the most widely deployed asymmetric cryptographic algorithm, used for digital signatures, key exchange, and encryption. This skill covers generating, storing, rotating, and managing RSA key pairs following NIST SP 800-57 key management guidelines, including key serialization formats (PEM, DER, PKCS#8), passphrase protection, and key strength validation.
When to Use
- When deploying or configuring implementing rsa key pair management capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Common Misconfigurations & Verification
- PKCS#1 v1.5 encryption (padding oracle):
RSA/PKCS1v15decryption that reveals padding-validity (via errors or timing) enables a Bleichenbacher attack to recover plaintext. Use RSA-OAEP (padding.OAEPwith SHA-256) for encryption, neverPKCS1v15for new systems. - PKCS#1 v1.5 signatures: prefer RSA-PSS for signing; if PKCS1v15 verification must stay for legacy, pin the exact hash and never mix.
- Key too small / weak: reject keys
<2048bits (use ≥3072 for new deployments). Validate the modulus bit length and run a weak-key check (small factors, low public exponent like e=3 with no OAEP, shared primes / ROCA). - Unprotected private key: encrypt private keys with a strong passphrase (
BestAvailableEncryption, AES-256) in PKCS#8, and store with0600permissions — never commit unencrypted PEMs. - No key rotation / versioning: rotate at least annually and retain old public keys for verifying historical signatures only.
- Mandatory tests: an RSA-PSS signature over a tampered message is REJECTED; verification with the wrong public key is REJECTED; OAEP decryption of a corrupted ciphertext fails cleanly without leaking padding state; loading the private key with a wrong passphrase fails;
key.key_size >= 3072is asserted.
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.
- 8d ago First seen · 104 lines · 50 tokens per session scan A 5e1e5784704a
implementing-rsa-key-pair-management is a skill published in the GitHub repository xalgorix/xalgorix (975 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,150 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-03.
Other skills, from other repositories
implementing-rsa-key-pair-management
RSA (Rivest-Shamir-Adleman) is the most widely deployed asymmetric cryptographic algorithm, used for digital signatures, key exchange, and encryption. This skill covers generating, storing, rotating.
configuring-certificate-authority-with-openssl
A Certificate Authority (CA) is the trust anchor in a PKI hierarchy, responsible for issuing, signing, and revoking digital certificates. This skill covers building a two-tier CA hierarchy (Root CA +.
configuring-hsm-for-key-storage
Hardware Security Modules (HSMs) are tamper-resistant physical devices that safeguard cryptographic keys and perform cryptographic operations in a hardened environment. Keys stored in an HSM never lea.
Cryptographic Analysis & Assessment
SSL/TLS auditing, cipher suite analysis, hash algorithm identification, encryption implementation review, and cryptographic weakness detection in code.
cryptography-expert
Expert in cryptographic algorithms, PKI, TLS/SSL, encryption standards, key management, and secure communication protocols. Use when the user mentions encryption, PKI, TLS, SSL, key management, or security, or when the task involves Cryptographic Fundamentals, Public Key Infrastructure, TLS/SSL Protocol, or Modern…
configuring-tls-1-3-for-secure-communications
TLS 1.3 (RFC 8446) is the latest version of the Transport Layer Security protocol, providing significant improvements over TLS 1.2 in both security and performance. It reduces handshake latency to 1-R.