Memstack Security Secrets Scanner

What it does

When your agent uses it

• The user says scan for secrets
• Check for leaked keys
• Secrets scanner
• Hardcoded credentials

Example prompts

• “scan for secrets”
• “check for leaked keys”
• “secrets scanner”
• “/memstack-security-secrets-scanner”

Requirements

• Python 3
• Docker
• A credential in STRIPE_SECRET_KEY

Workflow steps

11 steps, taken from the step headings in SKILL.md.

1. 1Scan for Hardcoded Secrets (Check 1)
2. 2Audit .env File Security (Check 2)
3. 3Scan Config and Documentation Files (Check 3)
4. 4Check Environment Variable Usage (Check 4)
5. 5Check Client-Side Secret Exposure (Check 5)
6. 6Scan Git History (Check 6)
7. 7Check Docker/Container Files (Check 7)
8. 8Generate Report
9. 9Generate .env.example
10. 10Pre-Rotation Checklist
11. 11Provide Recommendations

What it can do on your machine

Read from SKILL.md and the folder at commit 00370ce. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • python
  • stripe
  • vercel

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and vercel, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • STRIPE_SECRET_KEY
  • SUPABASE_SERVICE_ROLE_KEY
  • STRIPE_PUBLISHABLE_KEY
  • NEXT_PUBLIC_SUPABASE_ANON_KEY
  • NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY
  • STRIPE_WEBHOOK_SECRET

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Memstack Security Secrets Scanner loads about 6k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,874 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~71

When it runs · the whole SKILL.md, loaded when a task matches

~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:26

  | **User asks about .env security** | ACTIVE: targeted .env audit |

• NoteMentions a .env fileSKILL.md:28

  | **User is creating .env files** | DORMANT: let them work |

• NoteMentions a .env fileSKILL.md:54

  cut -d= -f1 .env | grep -vE '^#|^$' | sort

• NoteMentions a .env fileSKILL.md:57

  sed 's/=.*/=<redacted>/' .env

• NoteMentions a .env fileSKILL.md:60

  grep -qE '^VARNAME=.+' .env && echo set || echo unset

• NoteMentions a .env fileSKILL.md:63

  (KEY|SECRET|PASSWORD)=.*/\1=[REDACTED]/' .env

• NoteMentions a .env fileSKILL.md:66

  sed -E 's/=(.{6}).*/=\1…/' .env

• NoteMentions a .env fileSKILL.md:77

  awk -F= '/^VARNAME=/{print length($2)}' .env

• NoteMentions a .env fileSKILL.md:80

  grep '^VARNAME=' .env | cut -d= -f2- | tr -d '"' \

• NoteMentions a .env fileSKILL.md:84

  grep '^VARNAME=' .env | cut -d= -f2- | tr -d '"' | sha256sum | cut -c1-8

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Proprietary) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,874 words (~6,020 tokens).

name

memstack-security-secrets-scanner

version

1.0.0

license

Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/security/secrets-scanner of cwinvestments/memstack.

Open the folder on GitHubat commit 00370ce