Handles credentials safely through their whole life — where they live, how code gets them, how they rotate, and what to do when one leaks. Use this whenever the user is adding an API key, database password, token, or certificate, mentions a secrets manager or vault, asks how to store credentials, or has committed a secret to git. For finding exposed secrets during a code review, use security-analysis.
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
# Secrets management
A secret's danger is proportional to how many places it exists and how long it lives. Most
practice focuses on the first storage decision and ignores rotation and revocation, which is
where the real exposure sits — a key nobody has rotated in four years has been on more laptops
than anyone can name.
**Assume every secret will eventually leak.** Design so that when it does, the blast radius is
small and the fix is one command.
## 1. Prefer not having a secret at all
The best credential is one that does not exist. In order of preference:
1. **Workload identity**, the platform vouches for the service. IAM roles, service accounts,
OIDC federation. Nothing to store, nothing to rotate, nothing to leak
2. **Short-lived credentials** issued on demand, expiring in minutes or hours
3. **A long-lived secret in a manager**, injected at runtime
4. **A long-lived secret in an environment variable** — workable, and the floor
5. **A secret in a file in the repo**, never
Most cloud-to-cloud authentication can use option 1 today, and teams keep using static keys out
of habit. That is the single biggest available improvement.
…
The line at the top of this page pins the label git:20260828.866dec6, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5259 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
GitHub
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7mey2ng5knad4kwj
GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/secrets-management
GET https://markdownregistry.com/api/v1/blob/7f73b009fa9ccebdb5aa402560c2d4da517d0b1cb9793aa13c59a3795ee1dc31
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.
okhp3/skillz · .agents/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
okhp3/skillz · .agents/skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-artifact-validation/SKILL.md · Validate a project change, draft, research packet, skill, promotion package, or handoff before it is treated as…
okhp3/skillz · .agents/skills/okhp3-as-is-process-capture/SKILL.md · Capture and normalise a current-state process description into a structured as-is process YAML with stable step…
okhp3/skillz · .agents/skills/okhp3-brand-style-registry/SKILL.md · OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand…
okhp3/skillz · .agents/skills/okhp3-capture-intake/SKILL.md · Preserve one raw idea, file, link, transcript, or request in a project inbox with provenance and minimal handling. Use…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-builder/SKILL.md · Build, audit, and improve OpenAI Custom GPTs with production-grade methodology. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-readiness/SKILL.md · Assess an incomplete or newly proposed Custom GPT concept for build readiness. Use when a user has a GPT idea, partial…
okhp3/skillz · .agents/skills/okhp3-decision-model-authoring/SKILL.md · Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS…
okhp3/skillz · .agents/skills/okhp3-elicitation-interviews/SKILL.md · Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill…
nahid-sparktales/agent-dispatcher · skills/security/secrets-management/SKILL.md · Keep credentials out of code, logs, bundles and history — one supply path, scoped per environment, rotatable on demand…
aniruddhadas1/oniroute_swarmagents · skills/official/security/secrets-management/SKILL.md · Govern sensitive credentials across creation, storage, access, rotation, and retirement. Use for planning, evaluation…
