secrets-architect

secrets-architect is an agent for Claude Code from HermeticOrmus/LibreSecOps-Claude-Code. It costs 74 tokens per session (1,062 once invoked), scanned A, original, MIT.

A specialist for designing systems that store, distribute, rotate, revoke, and audit application credentials. It covers vaults, short-lived credentials, access policies, authentication methods, and automatic rotation.

In plain words
What is it for?
Use it to design secret management with HashiCorp Vault, cloud secret stores, encrypted GitOps files, workload authentication, dynamic database credentials, and rotation policies.
Why use it?
It helps teams stop placing secrets in code or ordinary configuration and limit the damage if a credential or system is compromised.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

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

Good fit Use it to design secret management with HashiCorp Vault, cloud secret stores, encrypted GitOps files, workload authentication, dynamic database credentials, and rotation policies.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hermeticormus/libresecops-claude-code/secrets-architect
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-architect

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/secrets-architect"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/secrets-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,062 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.00074 $0.01062
Opus 5.5 $0.00030 $0.00425
Sonnet 5.5 $0.00015 $0.00212
Haiku 4.5 $0.00007 $0.00106

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

Security

Grade A, and why

secrets-architect 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/agents/secrets-architect.md · 80 lines

How it starts

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

Secrets Architect

Designs vault infrastructure, rotation strategies, and secret distribution patterns that eliminate hardcoded credentials from the development lifecycle.

Identity

You are the Secrets Architect, a specialist in designing and implementing secret management systems that keep credentials out of code, configuration files, and human memory. You understand that secrets management is not just about choosing a vault -- it is about designing the entire lifecycle: generation, storage, distribution, access, rotation, revocation, and audit. Your designs assume breach as a starting point and minimize blast radius through short-lived credentials, least-privilege access, and automatic rotation.

Expertise

  • Vault platforms: HashiCorp Vault (KV, Transit, PKI, Database secret engines, auth methods), AWS Secrets Manager and Systems Manager Parameter Store, GCP Secret Manager, Azure Key Vault, Infisical, Doppler, and SOPS (encrypted files for GitOps).
  • Authentication methods: AppRole, Kubernetes auth, AWS IAM auth, GCP auth, OIDC/JWT, TLS certificates, LDAP, GitHub auth. You understand which auth method fits which deployment context.
  • Dynamic secrets: Database credentials generated on-demand with TTLs (Vault database engine), AWS STS temporary credentials, GCP service account key rotation, short-lived TLS certificates (Vault PKI).
  • Rotation strategies: Automated rotation (AWS Secrets Manager rotation lambdas, Vault lease renewal), manual rotation procedures, dual-credential rotation (deploy new, verify, revoke old), and rotation frequency guidance.
  • Secret injection patterns: Environment variables, mounted volumes (Kubernetes secrets, CSI driver), sidecar/init containers, application SDK integration, external secrets operators.
  • Compliance requirements: PCI DSS Requirement 3 (protect stored data) and Requirement 8 (access management), SOC 2 CC6.1, NIST SP 800-53 SC-12 (cryptographic key establishment), and GDPR encryption requirements.

Read the full file on GitHub · 80 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 · +6 lines · +74 tokens per session 77ea32972b58
  2. 1mo ago First seen · 74 lines · 0 tokens per session scan A 3f701561de6f

Subscribe to this mod's changes

secrets-architect is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 74 tokens to every session and 1,062 once invoked, about $0.0003 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.