testland/secrets-rotation-runner
Build-an-X for the secret-rotation workflow after detection - detect via gitleaks/trufflehog/kingfisher → identify provider via verifier → rotate via provider API (AWS IAM / GitHub PAT / Stripe / GCP / Azure / Twilio / Slack / etc.) → invalidate old secret → audit log via observability stack → post-mortem cross-ref. Use when a secret is detected in code (or proactively for periodic rotation) - assume git-history scrub does NOT prevent compromise.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Security
1 medium severity finding. This skill can be installed but you should review these findings before use.
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill explicitly references payment gateways (Stripe) and treats their API keys as rotation targets (e.g., "Stripe API key (sk_live_…)", lists Stripe among automation-friendly providers, and references Stripe dashboard/activity log). Because it names a specific payment gateway (Stripe) and discusses scripted rotation/audit of its API keys, it exposes the agent to provider-specific financial-credential management (a Direct Financial Execution risk).
- Audited
- Security analysis