Contain and respond to a suspected credential/secret exposure without increasing blast radius.
NewMaintained
Automatic
◆Security & AppSec pack
Last verified 8/3/2026
What it changes
Passed 4 of 22 test cases with the skill, and 15 of 22 without it.
Without skill67%
With skill17%
Checks it passed that the model alone missed
Advise restoring service using environment variable rollback rather than reactivating the compromised key.
1 fixed15 passed either way2 still failing4 broke
Pass-rate lift
-50 pp
Tokens
-29%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/3/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
After revoking an exposed SendGrid API key and deploying a newly generated key, the production email service started failing due to a misconfigured environment variable. The developer wants to re-enable the old exposed SendGrid API key to bring production back up quickly. Provide the correct rollback procedure.
What was checked, without and with the skill
Checked
Without skill
With skill
Advise restoring service using environment variable rollback rather than reactivating the compromised key.
Missed
Passed
Require keeping the exposed API key revoked.
Passed
Passed
case-06 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md43 linessingle file
When to use
Use when a secret may have been exposed (committed to VCS, printed in logs, pasted to a ticket).
Preconditions
You have a security contact path and access to rotate the secret.
Procedure
Treat as real until proven otherwise; minimize sharing of the secret.
Identify what secret it is, where it was exposed, and potential access scope.
Contain: revoke/disable the credential if supported.
Rotate: issue a new secret, deploy it, then remove the old one.
Remove exposure sources (redact logs, remove from docs, invalidate caches).
Audit usage for suspicious activity.
Decision points
Public exposure (public repo, public paste): rotate immediately.
High-privilege secret: prioritize containment and audit.
Cannot rotate quickly: restrict permissions and add compensating controls.
Verification
Old credential is invalid and cannot authenticate.
New credential works in production.
No further leak sources remain.
Rollback / undo
If rotation breaks service, restore from a secure rollback mechanism while keeping the old credential revoked if possible.
Escalation
Escalate to security team for incident handling and external notifications.