sota-secrets-management SKILL.md skillA
sota-secrets-management from martinholovsky/sota-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinholovsky/sota-skills/sota-secrets-management@git:20261027.0f83440Pins git:20261027.0f83440 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinholovsky/sota-skills
- Path
skills/sota-secrets-management/SKILL.md- Versions recorded
- 11
- Latest version
- git:20261027.0f83440, committed Oct 27, 2026
- First version recorded
- Jun 17, 2026
- Size
- 12,552 bytes
- Repository stars
- 26
- License
- CC-BY-4.0
State-of-the-art secrets management for building and auditing software. Use whenever a task involves creating, storing, injecting, rotating, or scanning for credentials — or reviewing code/infrastructure for secret leaks and misuse. BUILD mode: implementing secrets handling; AUDIT mode: sweeping a repo for leaked, hardcoded, or mishandled secrets. Trigger keywords: secret, secrets management, credential, API key, token, password, private key, signing key, JWT secret, TLS key, SSH key, database…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SOTA Secrets Management ## Purpose Eliminate static secrets where possible; where not possible, make every secret short-lived, narrowly scoped, runtime-injected, auditable, and rotatable without downtime. This skill covers the full lifecycle (generation → distribution → storage → use → rotation → revocation → expiry), storage backends, application handling patterns, leak detection, incident remediation, and per-credential-type rules. It serves two workflows: **BUILD** (write correct secrets handling into new or existing code) and **AUDIT** (sweep a repo for secret issues and report findings). The hierarchy of preference, always: 1. **No secret at all** — workload identity / OIDC federation / cloud IAM roles. 2. **Short-lived, auto-issued secret** — Vault dynamic creds, STS tokens, SPIRE SVIDs. 3. **Long-lived secret in a managed backend** — secret manager + rotation + audit log. 4. **Encrypted secret in the repo** — SOPS+age / sealed-secrets, GitOps only. 5. **Plaintext secret anywhere** — never acceptable. When you write or review code, push the design as far up this hierarchy as the platform allows, and document why if you stop below level 2. ## BUILD mode …
Read the whole file at its exact version.
How to install
mdr add martinholovsky/sota-skills/sota-secrets-management@sha256:62c70a094b85c459The line at the top of this page pins the label git:20261027.0f83440, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mtkf5pqwwcskl3vs)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Jun 17, 2026 and Oct 27, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.0f83440 latest | 2026-10-27 | 0f83440 | 12,552 B | A | view · diff |
| git:20261027.02e2698 | 2026-10-27 | 02e2698 | 12,506 B | A | view · diff |
| git:20261024.8dd2b0a | 2026-10-24 | 8dd2b0a | 12,426 B | A | view · diff |
| git:20261012.ae1b29b | 2026-10-12 | ae1b29b | 12,185 B | A | view · diff |
| git:20260926.1b7230a | 2026-09-26 | 1b7230a | 11,727 B | A | view · diff |
| git:20260925.467e225 | 2026-09-25 | 467e225 | 11,641 B | A | view · diff |
| git:20260907.41639b6 | 2026-09-07 | 41639b6 | 11,563 B | A | view · diff |
| git:20260709.6d10583 | 2026-07-09 | 6d10583 | 11,214 B | A | view · diff |
| git:20260701.1c5bd88 | 2026-07-01 | 1c5bd88 | 11,229 B | A | view · diff |
| git:20260629.bacf523 | 2026-06-29 | bacf523 | 11,186 B | A | view · diff |
| git:20260617.c5d2c7b | 2026-06-17 | c5d2c7b | 11,289 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12552 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
martinholovsky/sota-skills · 26 stars · license CC-BY-4.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mtkf5pqwwcskl3vs GET https://markdownregistry.com/api/v1/resolve?ref=martinholovsky/sota-skills/sota-secrets-management GET https://markdownregistry.com/api/v1/blob/62c70a094b85c4592ca1a63fb4f9d13b9f8e9516385890e6c57a22f332daab71
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.