Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cwinvestments/memstack/secrets-scannernpx skills add cwinvestments/memstack --skill secrets-scannergit clone --depth 1 https://github.com/cwinvestments/memstackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cwinvestments/memstack/secrets-scanner)<a href="https://agentmods.dev/skills/cwinvestments/memstack/secrets-scanner"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/secrets-scanner.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.06657 |
| Opus 5 | $0.00031 | $0.03328 |
| Sonnet 5 | $0.00012 | $0.01331 |
| Haiku 4.5 | $0.00006 | $0.00666 |
Grade B, and why
memstack-security-secrets-scanner scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Extract all env var names from the codebase Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔑 Secrets Scanner: Scanning for Exposed Credentials...
Scan a codebase for hardcoded secrets, leaked API keys, and credential exposure across files and git history.
Activation
When this skill activates, output:
🔑 Secrets Scanner: Scanning for Exposed Credentials...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User asks to scan for secrets/keys | ACTIVE: full scan |
| User mentions credential exposure | ACTIVE: full scan |
| User asks about .env security | ACTIVE: targeted .env audit |
| Pre-deployment security review | ACTIVE: full scan |
| User is creating .env files | DORMANT: let them work |
⚠️ Enforcement lives in CLAUDE.md, not here
This skill cannot be the control that prevents secret leaks. Skill matching is semantic and probabilistic: it misses. In a real session that leaked a live SendGrid production key, the query "rotate object storage credentials S3 bucket key move secrets rotation" scored this skill at 0.24 and it never loaded. The task was credential handling end to end.
Therefore the hard rule ("never print a secret value") belongs in always-loaded context,
a project CLAUDE.md block, which loads unconditionally regardless of matching, MCP
reachability, or hooks. This skill carries the operational how-to below; CLAUDE.md carries
the prohibition. If you are reading this skill and the project has no secrets block in
CLAUDE.md, adding one is the highest-value fix available, ahead of any scan.
Safe Inspection Patterns (use these any time you touch a secrets file)
Rule: allowlist names, never denylist values
Redaction by denylist is the single most common way secrets leak during "safe" inspection.
A pattern that redacts KEY=, SECRET=, PASSWORD= looks thorough and silently fails on
SENDGRID_API_KEY_PROD=, STRIPE_SECRET_KEY_TEST=, DB_PASSWORD_2=: any suffixed variant.
Never enumerate what to hide. Emit only what is provably safe: names.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed b293aa177475
- 3d ago First seen · 550 lines · 62 tokens per session scan B f2c5a5fee5d5
memstack-security-secrets-scanner is a skill published in the GitHub repository cwinvestments/memstack (419 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 6,657 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
git-commit-generator
Generate Conventional Commits from staged git diff. Analyzes changes and produces commit messages following the Conventional Commits spec (feat, fix, refactor, etc.). Triggers on "generate commit", "write commit message", "conventional commit".
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
polyphony
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches.