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/hermeticormus/libresecops-claude-code/key-managementnpx skills add HermeticOrmus/LibreSecOps-Claude-Code --skill key-managementgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/key-management)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/key-management"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/key-management.svg" alt="Measured on agentmods" 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.00000 | $0.02901 |
| Opus 5 | $0.00000 | $0.01451 |
| Sonnet 5 | $0.00000 | $0.00580 |
| Haiku 4.5 | $0.00000 | $0.00290 |
Grade A, and why
key-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 5d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Key Management
Key lifecycle management, rotation strategies, storage options, and operational security for cryptographic keys.
Knowledge Base
Key Lifecycle
Every cryptographic key goes through a lifecycle. Each phase has security requirements:
Generation → Distribution → Storage → Use → Rotation → Revocation → Destruction
| | | | | | |
v v v v v v v
CSPRNG Secure channel Encrypted Audit New key Notify Crypto-
or HSM or KMS API at rest trail replaces relying shred
old parties
Key Types and Their Roles
| Key Type | Abbreviation | Purpose | Lifecycle |
|---|---|---|---|
| Master Key | MK | Protects other keys. Never used for data directly. | Years. Stored in HSM. Rarely rotated. |
| Key Encryption Key | KEK | Encrypts Data Encryption Keys (envelope encryption). | Months to years. Stored in KMS. |
| Data Encryption Key | DEK | Encrypts actual data. | Per-operation or per-session. Generated and used in memory. |
| Signing Key | SK | Creates digital signatures. | Months to years. Private key highly protected. |
| TLS Private Key | -- | Authenticates server in TLS handshake. | 1-2 years (certificate lifetime). |
| API Key | -- | Authenticates API clients. | 90 days recommended rotation. |
| Session Key | -- | Encrypts a single session (TLS, SSH). | Minutes to hours. Ephemeral. |
Storage Security Hierarchy
Listed from most secure to least secure:
| Storage | Security Level | Use Case | Cost |
|---|---|---|---|
| HSM (Hardware Security Module) | Highest. Key never leaves the HSM boundary. FIPS 140-2/3 Level 3. | Master keys, CA keys, payment processing keys | $$$$ |
| Cloud KMS (AWS KMS, GCP KMS, Azure Key Vault) | High. Keys managed by cloud provider in HSMs. API-accessed. | KEKs, signing keys, envelope encryption | $$ |
| Secrets Manager (AWS Secrets Manager, HashiCorp Vault) | Medium-High. Encrypted storage with access control, rotation. | API keys, database passwords, service credentials | $$ |
| Encrypted file on disk | Medium. Only as secure as the encryption key and file permissions. | Development environments, backup keys | $ |
| Environment variable | Low. Visible in process listings, crash dumps, CI logs. | Injection point only (value comes from secrets manager). | Free |
| Source code / config file | NONE. Public to anyone with repo access. In git history forever. | NEVER | Free |
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.
- 5d ago First seen · 278 lines · 0 tokens per session scan A 934ee4220a1a
key-management is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,901 tokens. 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-31.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.