secrets-with-git-crypt SKILL.md skillA
secrets-with-git-crypt from derailed-dash/dazbo-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add derailed-dash/dazbo-agent-skills/secrets-with-git-crypt@git:20261107.6674a9fPins git:20261107.6674a9f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- derailed-dash/dazbo-agent-skills
- Path
skills/secrets-with-git-crypt/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261107.6674a9f, committed Nov 7, 2026
- First version recorded
- May 30, 2026
- Size
- 8,829 bytes
- Repository stars
- 27
- License
- MIT
Manages encryption and decryption of repository secrets (such as .env or *.tfvars) using git-crypt, keeping credentials secure with parallel encrypted files. Use when managing secrets, setting up git-crypt, or encrypting/decrypting environment files.
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 with Git-Crypt This skill provides a secure, structured workflow for managing repository secrets (e.g. `.env`, `*.tfvars`, `sec.json`, `settings.json`) using `git-crypt`. It guides the agent to ensure sensitive credentials are never checked in as plaintext, instead maintaining parallel encrypted `.enc` versions checked into Git. ## Table of Contents - [Triggers](#triggers) - [Prerequisites](#prerequisites) - [Secrets Setup and Sync Workflow](#secrets-setup-and-sync-workflow) - [Command Reference](#command-reference) - [Verification Loop](#verification-loop) ## Triggers This skill MUST trigger whenever: - The user mentions `git-crypt`, `encryption`, `decryption`, or `secrets management`. - The user requests to store sensitive files (like `.env`, `*.tfvars`, `settings.json`, keyfiles) in the repository. - The user attempts to commit or push files that should be encrypted (e.g. `.env`, `*.tfvars`, `sec.json`) to the repository. - Cloning an existing repository that contains `.enc` files (e.g. `.env.enc`, `terraform.tfvars.enc`, `settings.json.enc`), indicating it was previously protected by git-crypt. …
Read the whole file at its exact version.
How to install
mdr add derailed-dash/dazbo-agent-skills/secrets-with-git-crypt@sha256:8ffbf62ee46ce89bThe line at the top of this page pins the label git:20261107.6674a9f, 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_eb6eo7jkmw3mtt7v)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 30, 2026 and Nov 7, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.6674a9f latest | 2026-11-07 | 6674a9f | 8,829 B | A | view · diff |
| git:20261107.a37ac20 | 2026-11-07 | a37ac20 | 7,959 B | A | view · diff |
| git:20260804.cb63bb6 | 2026-08-04 | cb63bb6 | 7,285 B | A | view · diff |
| git:20260706.b7b7b13 | 2026-07-06 | b7b7b13 | 6,647 B | A | view · diff |
| git:20260530.603e4ba | 2026-05-30 | 603e4ba | 6,533 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 (8829 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
derailed-dash/dazbo-agent-skills · 27 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eb6eo7jkmw3mtt7v GET https://markdownregistry.com/api/v1/resolve?ref=derailed-dash/dazbo-agent-skills/secrets-with-git-crypt GET https://markdownregistry.com/api/v1/blob/8ffbf62ee46ce89b97c003ad6a0f91d5dbc2cb6cdf4dca121110a39057790994
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.