secrets-in-git-history SKILL.md skillA
secrets-in-git-history from tonydzi/second-brain-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tonydzi/second-brain-starter-kit/secrets-in-git-history@git:20261020.402f6b7Pins git:20261020.402f6b7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tonydzi/second-brain-starter-kit
- Path
skills/secrets-in-git-history/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261020.402f6b7, committed Oct 20, 2026
- First version recorded
- Sep 24, 2026
- Size
- 14,462 bytes
- Repository stars
- 14
- License
- MIT
- Mine GitHub, GitLab and git history for identities, infrastructure and leaked credentials using commit author emails, GitHub code search, the commit… Use when investigating a developer or organisation on GitHub, finding leaked API keys, AWS keys or tokens in code, enumerating org members and their personal repos, or recovering secrets deleted from HEAD but still present in history or forks.
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 in git history A repository is three intelligence products: a list of humans with real email addresses, a map of the organisation's infrastructure, and a credential store nobody meant to publish. The costly mistake is scanning the working tree. Secrets deleted from HEAD stay in history forever, and commits deleted from a branch stay reachable through the fork network — scan only what is checked out and you are searching the one place the secret was definitely removed from. ## What you're holding, and where to start | You have | Start with | Why | |---|---|---| | An organisation name | Public org members, then their personal repos | Corporate repos are reviewed; personal ones are not | | A developer's name or handle | Commit emails across their repos | Yields an email nothing else gives you | | A commit email | Reverse-search across hosts; resolve any noreply ID | Links accounts across orgs and platforms | | A suspected credential leak | Both scanners over a mirror clone, all refs | HEAD-only scanning misses the point entirely | | A specific string — hostname, key prefix | `git log -S` pickaxe across all refs | Tells you when it entered and when it left | …
Read the whole file at its exact version.
How to install
mdr add tonydzi/second-brain-starter-kit/secrets-in-git-history@sha256:b9b59af9432c2280The line at the top of this page pins the label git:20261020.402f6b7, 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_go33xthydrq5a6un)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 24, 2026 and Oct 20, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.402f6b7 latest | 2026-10-20 | 402f6b7 | 14,462 B | A | view · diff |
| git:20261007.cd6c208 | 2026-10-07 | cd6c208 | 14,468 B | A | view · diff |
| git:20261003.a2d662f | 2026-10-03 | a2d662f | 14,469 B | A | view · diff |
| git:20260924.2784cb2 | 2026-09-24 | 2784cb2 | 13,354 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 (14462 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
tonydzi/second-brain-starter-kit · 14 stars · license MIT · pushed 2026-11-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_go33xthydrq5a6un GET https://markdownregistry.com/api/v1/resolve?ref=tonydzi/second-brain-starter-kit/secrets-in-git-history GET https://markdownregistry.com/api/v1/blob/b9b59af9432c2280c97f0107edf99ad244094255095f560333647fef4cfdf0c7
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.