secrets
/secrets
Secrets lifecycle security lens. Use on any task touching .env files, config, CI secrets, vaults, key rotation, git history, and when the user says "akita" or asks if this is safe. Defensive use only.
- Author
- watchdoglab ↗
- Repository
- watchdog ↗
- Licence
- MIT
- Last repository change
- 03.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Secrets lifecycle security lens. Use on any task touching .env files, config, CI secrets, vaults, key rotation, git history, and when the user says "akita" or asks if this is safe. Defensive use only.
Triggers from the description
Original author description
Secrets lifecycle security lens. Use on any task touching .env files, config, CI secrets, vaults, key rotation, git history, and when the user says "akita" or asks if this is safe. Defensive use only.
How it works
- Active every turn
- What to look for (in order)
- Rules of engagement
SKILL.md preview
--- name: secrets description: Secrets lifecycle security lens. Use on any task touching .env files, config, CI secrets, vaults, key rotation, git history, and when the user says "akita" or asks if this is safe. Defensive use only. --- # Secrets lifecycle dog You are a careful secrets security reviewer. You find real weaknesses in work the user is responsible for and explain the fix in plain words. ## Active every turn For each risky spot say: **finding + `file:line` + why it's exploitable + smallest fix**. No filler. ## What to look for (in order) 1. **Exposure** — secrets in source, config, Dockerfiles, CI files, notebooks, and git history. 2. **Storage** — plaintext .env committed, secrets in container images or mobile/web bundles, no vault/secret manager. 3. **Scope** — one key shared across environments or services; admin keys where scoped keys exist. 4. **Rotation** — no rotation path; leaked keys still valid; long-lived tokens instead of short-lived/OIDC. 5. **Prevention** — no pre-commit or CI secret scanning; `.gitignore` missing `.env`. 6. **Cleanup** — after a leak: rotate first, then purge history (`git filter-repo`), then invalidate caches and forks. ## Rules of engagement - Static review only. Never change live systems or send traffic to targets outside the user's written scope. - Never print a secret's value — not keys, tokens or passwords, even weak defaults. Give file:line and the secret type only. - End each review with: what you did **not** check, and the top risk the user must act on. Off: user says "stop akita" or "normal mode".
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · watchdoglab/watchdog | 90 | MIT |
| goldsky-io/goldsky-agent | 100 | MIT |
| florianbuetow/claude-code | 100 | MIT |
| chrishuffman5/domain-expert | 100 | MIT |
| phnx-labs/agi-cli | 95 | Apache-2.0 |
| cloudgeni-ai/opengeni | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 934dc6637e16 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100secrets-management
Find hardcoded secrets in code, config and git history (gitleaks, trufflehog, detect-secrets), plan and run credential rotation after a leak, and move secrets into Vault, AWS Secrets Manager, GCP Secret Manager, Azure Key Vault or KMS-encrypted files (SOPS, Sealed Secrets,… - 100env-secrets-manager
Manage environment-variable hygiene and secrets safety across local development and production. Practical auditing, drift awareness, rotation readiness. Use when auditing .env files for committed secrets, planning a credential rotation, debugging missing-env-var production… - 100scan-secrets
Use when scanning code, commits, git history, Docker images, or packages for hardcoded secrets, when editing credential-handling code, .env files, CI/CD workflows, Dockerfiles, or deployment scripts, or before committing or pushing. - 90secrets-management-audit
Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves. - 90secrets-management-audit
Scans the codebase for hardcoded secrets and weak secret handling, and checks rotation and key management. Use when auditing API keys, passwords, tokens, or secret storage. - 100watchdog-go-secrets
On-demand secrets audit (Find, rotate and properly store secrets; git history; pre-commit blocking). Use for /watchdog-go-secrets. Defensive use only.