env-setup SKILL.md skillB
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
env-setup from mgiovani/ai-arsenal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mgiovani/ai-arsenal/env-setup@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mgiovani/ai-arsenal
- Path
skills/env-setup/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.0, committed Oct 5, 2026
- First version recorded
- Jul 19, 2026
- Size
- 7,486 bytes
- Repository stars
- 8
- License
- MIT
Scans a codebase for environment variable usage to generate or sync .env.example, validate .env completeness against what the code actually reads, and detect leaked secrets in .env or git history. Use for "/env-setup", "update .env.example", "sync .env.example with the codebase", "check if .env has everything it needs", "is .env in .gitignore", or "scan for leaked secrets in .env". Not a full security audit (use review-security for OWASP-level scanning) and not a generic secret-rotation or…
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
# Env Setup Scan the codebase for environment variable usage, generate or update `.env.example`, validate `.env` completeness, and detect leaked secrets. ## Anti-hallucination guidelines Only report variables that are actually found in the code: 1. Grep before reporting: never invent variable names, only list what grep actually returns. 2. Read `.env.example` before writing: preserve existing entries, only add/update what changed. 3. No actual secrets: `.env.example` must only contain placeholder values (e.g., `your_api_key_here`). 4. Verify `.gitignore`: actually read the file before claiming `.env` is ignored. 5. Never echo a found secret value: when Phase 6 flags a leaked secret, report the variable name and `file:line` only. Never print, quote, or write the actual value into chat output, a report file, or anywhere else: the scan's job is to locate leaks, not to create a second one. ## Workflow ### Phase 1: Scan Codebase …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uq7qstievke4tiyo/2c055e3fde415629c259336a7154aa0ed3b6f33fcefd0c431511917c215d5320.json
Then /plugin install env-setup@markdownregistry-uq7qstievke4tiyo in Claude Code. It installs v1.1.0, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add mgiovani/ai-arsenal/env-setup@sha256:2c055e3fde415629The line at the top of this page pins the label v1.1.0, 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_uq7qstievke4tiyo)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mgiovani/ai-arsenal/env-setup since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of env-setup from somewhere else? Ask it: where did my env-setup come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jul 19, 2026 and Oct 5, 2026, about one every 19 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-05 | b620662 | 7,486 B | B | view · diff |
| v1.1.0 | 2026-09-25 | ca015cc | 6,564 B | B | view · diff |
| v1.1.0 | 2026-09-16 | 0d6e629 | 6,580 B | B | view · diff |
| v1.1.0 | 2026-07-27 | fa2e9cf | 6,487 B | B | view · diff |
| v1.1.0 | 2026-07-19 | 4ee8666 | 6,544 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/env-setup/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: Read `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7486 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 base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
mgiovani/ai-arsenal · 8 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uq7qstievke4tiyo GET https://markdownregistry.com/api/v1/resolve?ref=mgiovani/ai-arsenal/env-setup GET https://markdownregistry.com/api/v1/blob/2c055e3fde415629c259336a7154aa0ed3b6f33fcefd0c431511917c215d5320
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.
More from mgiovani/ai-arsenal
Every file in mgiovani/ai-arsenal