Home / microsoft / waza · GitHub

secret-handling SKILL.md skillF

This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.

secret-handling from microsoft/waza is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add microsoft/waza/secret-handling@git:20261016.42d1b9f

Pins git:20261016.42d1b9f in mdr.lock. Pin the fingerprint instead.

Audit grade: F, 15 of 17 checks passed
Kind: SKILL.md skill
Repository: microsoft/waza
Path: .github/skills/secret-handling/SKILL.md
Versions recorded: 1
Latest version: git:20261016.42d1b9f, committed Oct 16, 2026
Size: 7,524 bytes
Repository stars: 1,424
License: MIT

Never read .env files or write secrets to .squad/ committed 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

## Context

Spawned agents have read access to the entire repository, including `.env` files containing live credentials. If an agent reads secrets and writes them to `.squad/` files (decisions, logs, history), Scribe auto-commits them to git, exposing them in remote history. This skill codifies absolute prohibitions and safe alternatives.

## Patterns

### Prohibited File Reads

**NEVER read these files:**
- `.env` (production secrets)
- `.env.local` (local dev secrets)
- `.env.production` (production environment)
- `.env.development` (development environment)
- `.env.staging` (staging environment)
- `.env.test` (test environment with real credentials)
- Any file matching `.env.*` UNLESS explicitly allowed (see below)

**Allowed alternatives:**
- `.env.example` (safe — contains placeholder values, no real secrets)
- `.env.sample` (safe — documentation template)
- `.env.template` (safe — schema/structure reference)

**If you need config info:**
1. **Ask the user directly** — "What's the database connection string?"
2. **Read `.env.example`** — shows structure without exposing secrets
3. **Read documentation** — check `README.md`, `docs/`, config guides
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add microsoft/waza/secret-handling@sha256:b59ecbc69e0e5d29

The line at the top of this page pins the label git:20261016.42d1b9f, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_6nmfrarybghq52ti.svg)](https://markdownregistry.com/a/art_6nmfrarybghq52ti)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 16, 2026.

version	committed	commit	size	audit
git:20261016.42d1b9f latest	2026-10-16	42d1b9f	7,524 B	F	view

Audit of the latest version

F 15 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

FAIL, critical: No credential-shaped string (matched: -----BEGIN PRIVATE KEY-----)
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 (7524 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 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

GitHub

microsoft/waza · 1,424 stars · license MIT · pushed 2026-10-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_6nmfrarybghq52ti
GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/waza/secret-handling
GET https://markdownregistry.com/api/v1/blob/b59ecbc69e0e5d295f0dcf6a90cd555e86c244eaacef786a753fca0e78ea8765

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 microsoft/waza

squad-commands SKILL.md skill

microsoft/waza · .copilot/skills/squad-commands/SKILL.md · Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when…

git:20260615.284ec6d · audit A · 1,424 stars

agent-collaboration SKILL.md skill

microsoft/waza · .github/skills/agent-collaboration/SKILL.md · Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication