secrets-rotate

secrets-rotate is a command for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 37 tokens per session (970 once invoked), scanned A, original, MIT.

A command that plans and documents how to replace credentials with new values. It covers cases such as a confirmed leak, scheduled maintenance, an employee leaving, compliance requirements, or an incident.

In plain words
What is it for?
Use it to plan rotation for cloud keys, database passwords, API keys, TLS certificates, CI/CD secrets, infrastructure settings, and third-party integrations.
Why use it?
Replacing a credential limits the damage when it may have been exposed or when someone should no longer have access. The plan also tracks where the old value is used so services do not break unexpectedly.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the secrets-management plugin — 2 skills, 2 commands, 2 agents shipped together

Good fit Use it to plan rotation for cloud keys, database passwords, API keys, TLS certificates, CI/CD secrets, infrastructure settings, and third-party integrations.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hermeticormus/libresecops-claude-code/secrets-rotate
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-Code

Made for: Claude Code.

Or install secrets-management, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 2 agents.

Wrote 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.

agentmods badge for secrets-rotate

README.md
[![agentmods](https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/secrets-rotate/github.svg)](https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/secrets-rotate)
Your own site
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/secrets-rotate"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/secrets-rotate/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.

agentmods 80×15 button for secrets-rotate

Your own site · 80×15
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/secrets-rotate"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/secrets-rotate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 970 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00970
Opus 5.5 $0.00015 $0.00388
Sonnet 5.5 $0.00007 $0.00194
Haiku 4.5 $0.00004 $0.00097

Measured 12d ago against content hash a1ceb989c4e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

secrets-rotate 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 12d 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.

plugins/secrets-management/commands/secrets-rotate.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/secrets-rotate

Plan and document a secret rotation procedure for identified credentials.

Trigger

Use when you need to rotate one or more credentials, whether due to:

  • Confirmed credential leak (immediate rotation required)
  • Scheduled rotation (periodic hygiene)
  • Employee departure (access revocation)
  • Compliance requirement (PCI DSS, SOC 2 mandated rotation)
  • Security incident response

Input

  • Required: The type of credential to rotate (AWS key, database password, API key, TLS certificate, etc.)
  • Required: The current context -- where the credential is used (which services, environments, configurations)
  • Optional: --emergency -- skip validation steps, prioritize speed over safety (for confirmed leaks)
  • Optional: --service [name] -- scope rotation to a specific service or environment

Process

  1. Credential Inventory: Identify all locations where the credential is used:

    • Application configuration (environment variables, config files, vault entries)
    • CI/CD pipelines (GitHub Secrets, GitLab CI Variables, Jenkins Credentials)
    • Infrastructure (Terraform state, Kubernetes secrets, cloud provider configurations)
    • Third-party integrations (webhooks, API callbacks, partner configurations)
    • Documentation and runbooks (if credentials were unfortunately documented)
  2. Impact Assessment: Determine what breaks if the old credential is revoked:

    • Which services depend on this credential?
    • Are there multiple environments (dev, staging, production) using the same credential?
    • Are there external partners or third-party services using this credential?
    • What is the expected downtime window?
  3. Rotation Strategy Selection:

    Dual-Credential Rotation (preferred, zero-downtime):

    • Generate new credential
    • Deploy new credential alongside old (both are valid)
    • Update all consumers to use new credential
    • Verify all consumers work with new credential
    • Revoke old credential

Read the full file on GitHub · 123 lines

Changes

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.

  1. 12d ago Changed · +5 lines · +37 tokens per session a1ceb989c4e9
  2. 1mo ago First seen · 118 lines · 0 tokens per session scan A b90b835ee3cb

Subscribe to this mod's changes

secrets-rotate is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 970 once invoked, about $0.0001 per session on Opus 5.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.