secret-scanning SKILL.md skillA
secret-scanning from valtterimelkko/agent-workflow-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add valtterimelkko/agent-workflow-skills/secret-scanning@git:20261028.95acd2fPins git:20261028.95acd2f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- valtterimelkko/agent-workflow-skills
- Path
skills/secret-scanning/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261028.95acd2f, committed Oct 28, 2026
- First version recorded
- Sep 30, 2026
- Size
- 5,636 bytes
- Repository stars
- 2
- License
- MIT
Scan git repos and directories for committed credentials with gitleaks and keep credentials out of repos. Use before making a repository public, before a new repo's first push, before copying evidence, logs, transcripts or skills into a repo, when adding secret scanning to CI or a pre-commit hook, when auditing a public repo's history, and whenever a task handled credential copies (auth.json, models.json with apiKey). Also for 'is this safe to publish?', 'did we leak a key?', gitleaks.
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
# Secret scanning
The goal is to keep credentials out of repositories. Scanning is the check; the
design rule comes first:
> **Credentials live outside the repo tree.** Code reads them from paths or
> environment variables that point outside the repository (for example
> `$HOME/.pi-web-ui/internal-api-token`), and should refuse a credential path that
> resolves inside its own repo. `.gitignore` is only a backstop: one `git add -f`
> or one renamed file defeats it.
## The tool: gitleaks
`gitleaks` is a single binary and needs no account or human step. Check it with
`gitleaks version`. If it is missing, install a pinned release and verify the checksum:
```bash
V=8.30.1; D=$(mktemp -d); cd "$D"
curl -sSfL -o gl.tgz "https://github.com/gitleaks/gitleaks/releases/download/v$V/gitleaks_${V}_linux_x64.tar.gz"
curl -sSfL -o sums.txt "https://github.com/gitleaks/gitleaks/releases/download/v$V/gitleaks_${V}_checksums.txt"
grep "gitleaks_${V}_linux_x64.tar.gz" sums.txt | sed "s/gitleaks_${V}_linux_x64.tar.gz/gl.tgz/" | sha256sum -c -
tar xzf gl.tgz gitleaks && install -m 0755 gitleaks /usr/local/bin/gitleaks; cd /; rm -rf "$D"
```
## Never print a secret
…Read the whole file at its exact version.
How to install
mdr add valtterimelkko/agent-workflow-skills/secret-scanning@sha256:25b18d1a87df4ee9The line at the top of this page pins the label git:20261028.95acd2f, 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_fcynogblc5375wwr)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 30, 2026 and Oct 28, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.95acd2f latest | 2026-10-28 | 95acd2f | 5,636 B | A | view · diff |
| git:20261028.fd27c08 | 2026-10-28 | fd27c08 | 5,576 B | A | view · diff |
| git:20260930.7c77a33 | 2026-09-30 | 7c77a33 | 5,500 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 (5636 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
valtterimelkko/agent-workflow-skills · 2 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fcynogblc5375wwr GET https://markdownregistry.com/api/v1/resolve?ref=valtterimelkko/agent-workflow-skills/secret-scanning GET https://markdownregistry.com/api/v1/blob/25b18d1a87df4ee92386369a494951ae594562c91058996b74c0cede2468e9cd
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 valtterimelkko/agent-workflow-skills
Every file in valtterimelkko/agent-workflow-skills