Works with the AI Agents you already use
Srednoff Secret Leak Incident Response Planner
Build a redacted revoke-first containment and consumer-cutover plan, with explicit authorization boundaries and an old-credential-failure/new-credential-success evidence ledger; no revocation is executed.
$9.99
Srednoff Secret Leak Incident Response Planner
Example session with this skill installed
Plan containment for a redacted exposed service token without contacting its provider.
- Read your context and instructions
- Compiled the srednoff secret leak
Expected report shape, not a completed real audit: Executive Summary; Scope; Assets / Trust Boundaries
Connects securely to your tools. The creator never sees your data.
About this skill
Srednoff Secret Leak Incident Response Planner
One-Line Outcome
Build a redacted revoke-first containment and consumer-cutover plan, with explicit authorization boundaries and an old-credential-failure/new-credential-success evidence ledger; no revocation is executed.
Short Description
Deleting a leaked value can leave active access, orphaned consumers and an unsafe rollback path; a premature rotation can also break dependencies without containing the compromised identity.
Problem It Solves
Deleting a leaked value can leave active access, orphaned consumers and an unsafe rollback path; a premature rotation can also break dependencies without containing the compromised identity.
Incident commander: secret-class/blast-radius containment runbook, revoke-first rotation/deployment dependency plan, old-key-failure/new-key-success validation ledger and Git-copy appendix.
What You Get
- Executive Summary
- Scope
- Assets / Trust Boundaries
- Evidence Reviewed
- Incident Timeline And Credential Classes
- Findings
- Containment And Consumer Cutover Plan
- Old Failure / New Success Ledger
- Git And Other Copy Appendix
- Critical Findings
- Quick Wins
- Prioritized Remediation Plan
- Missing Evidence
- Residual Risk
- Verification Checklist
How It Works
- Open a bounded incident record and freeze the evidence time/revision. Use credential class and opaque reference only; redact payloads before review and do not read secret stores.
- Separate confirmed exposure, plausible access, scanner candidate and known synthetic fixture. A credible real exposed credential is treated as compromised; no online validity check is needed to start containment planning.
- Map the identity's effective permissions, environments, data/services, derived sessions and signing trust. Bound known blast radius separately from unknown grants and missing audit coverage.
- Recommend revocation/disablement as the first containment objective, before Git cleanup or preventive work. Identify the authorized owner and exact provider resource; do not issue provider calls. Any continuity exception must be explicit, time-bounded and not mislabeled containment complete.
- Classify credential semantics: revoking an API token, rotating a database login and replacing a signing key have different downstream effects. Determine whether issued sessions, refresh tokens, cached credentials or signatures survive the parent change.
- Prepare an independently authorized replacement with minimal necessary scope and a trusted delivery channel. Do not generate, paste, transmit or place new credentials in this report; reference secure-store version IDs only.
- Build a consumer dependency table covering services, CI, scheduled jobs, previews, webhooks and recovery tooling. Name restart/reload/connection-pool requirements, ordering, owners and an availability checkpoint for each consumer.
- Inventory accessible copies in Git refs, artifacts, logs, traces, tickets, caches and backups using sanitized evidence. Import concept62's Git appendix into this same incident; inaccessible copies remain unresolved, not erased by assumption.
- Specify old-credential rejection validation by the authorized responder using a provider-supported non-destructive path, plus new-credential success for each required consumer. Distinguish authorization failure from timeout, wrong endpoint and missing test evidence.
- Review audit evidence around the bounded exposure window for misuse indicators without equating absent logs to no compromise. Record logging gaps, derived credential investigation and owner/legal escalation needs without asserting a breach beyond evidence.
- Define safe recovery: repair consumer configuration or issue another clean replacement; never restore the compromised credential as rollback. Preserve sensitive forensic records only under the owner's retention/access policy and never in the public report.
- Return containment status, prioritized actions, exact execution approvals still needed, residual copies and revalidation triggers. Close only the evidenced objectives; preventive controls and history cleanup do not substitute for revocation.
Best For
Incident commanders and service owners coordinating a confirmed or credibly suspected credential exposure
Example Tasks
- Plan containment for a redacted exposed service token without contacting its provider.
- Review our incident cutover evidence and unresolved old-key rejection checks.
Inputs
- Incident ID, detection and exposure timestamps/timezone, credential class and non-secret provider resource identifier; never the credential value.
- Sanitized exposure locations and scope, known account/environment/principal permissions, owner and separately authorized responder contacts.
- Consumer/deployment inventory, refresh/cache/derived-session behavior, availability constraints and permitted evidence roots/revisions.
- Redacted provider revocation/rotation receipts, deploy revisions and validation records if available; their absence remains explicit.
Outputs
- Executive Summary
- Scope
- Assets / Trust Boundaries
- Evidence Reviewed
- Incident Timeline And Credential Classes
- Findings
- Containment And Consumer Cutover Plan
- Old Failure / New Success Ledger
- Git And Other Copy Appendix
- Critical Findings
- Quick Wins
- Prioritized Remediation Plan
- Missing Evidence
- Residual Risk
- Verification Checklist
Permissions
Read-only review of owner-supplied artifacts by default. Report file writes, shell/local fixture execution and official documentation lookup are optional, require available tools and their explicit scope. No live credentials are requested.
Compatibility
Standalone workflow, no Srednoff OS dependency. Codex evidence is synthetic entrypoint text only when recorded below. Claude Code, Cursor and actual buyer-runtime task delivery remain UNTESTED. Provider/platform-specific contracts must be refreshed for the installed version.
Limitations
This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.
Validation Transparency
Offline evidence-precheck status: PASS. Authored synthetic text-response cases: 24/24, status PASS. This is not independent security testing, complete artifact inspection or proof of deployment safety. Exact-text hashes and attempts are retained separately.
License And Publisher
Commercial License 1.0 covers original new expression; historical MIT and third-party rights remain unchanged. Mandatory marketplace conditions prevail. Publisher: Ivan Srednoff / Srednoff.Agency. No proprietary source resale or off-platform paid upsell is included.
FAQ
What is different from a generic security request? Incident commander: secret-class/blast-radius containment runbook, revoke-first rotation/deployment dependency plan, old-key-failure/new-key-success validation ledger and Git-copy appendix. No automatic credential revocation, active secret retrieval, history rewrite, service downtime action or claim that deleting Git content remediates compromise.
Does it change production automatically? No. Audit/design is the default; changes, secret rotation, IAM, network probes and financial actions need separate explicit authorization.
Are the examples real incidents? No. They are synthetic DEMO DATA.
Is this a certification or guaranteed protection? No. Evidence gaps, residual risk and unexecuted tests remain explicit.
Can I use project-specific reports for clients? Yes under the included license; proprietary workflow source is not a client deliverable.
Version
1.0.0
Release Notes
Initial scoped security workflow with domain decision rules, evidence requirements, synthetic examples, regression cases and explicit authorization/runtime limits. No production/customer outcome is claimed.
This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago