---
title: "Credential lifecycle and leak-response planner: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/agency-security-secrets-credential-engineer/
description: "A credential-lifecycle profile connecting detection, ownership, provider revocation and controlled rotation."
---

# Credential lifecycle and leak-response planner: review, role & definition · Undominated.ai

> A credential-lifecycle profile connecting detection, ownership, provider revocation and controlled rotation.

[← Explore all agents](/agents/)

SECURITY OPERATIONS / Agency Agents community

# Credential lifecycle and leak-response planner

A credential-lifecycle profile connecting detection, ownership, provider revocation and controlled rotation.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Agency Agents community
 Licence [MIT ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE)
 Revision bd956db032d9
 [Read what was—and wasn’t—checked ↓](#review)

“Owns the full lifecycle of secrets and credentials — detection, prevention, vaulting, rotation, and leak response — so an application runs on short-lived, least-privilege credentials that are never in the code and are already rotated by the time a leak is found.”

 [Agency Agents community · upstream description ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It distinguishes removing a key from source from revoking it at the provider and asks for an exposure-window usage audit.
- Its database example explicitly limits grants to existing tables and calls out sequence privileges and future-table policy as separate checks.

### A good fit for

 - Supply redacted credential inventory, workload ownership and provider-specific revocation procedures.
- Produce a lifecycle inventory, scanning plan and leak-response runbook without reproducing secret values.

### Weigh up before choosing

 - Short lifetimes do not make blast radius near zero; sample scanner versions and grants require environment-specific verification. Revocation, deployment and history rewriting are consequential actions.
- Source-only component: inspect its upstream context and dependencies before adapting it; no standalone runnable bundle is offered.
- Native-host parsing and loading of the original Agency frontmatter were not tested. Check the installed host requirements; optional metadata may be ignored rather than enforced.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - security/security-secrets-credential-engineer.md (pinned complete source retained)
- LICENSE
- Repository README and current official host configuration documentation

### Our findings

 - It distinguishes removing a key from source from revoking it at the provider and asks for an exposure-window usage audit.
- Its database example explicitly limits grants to existing tables and calls out sequence privileges and future-table policy as separate checks.

### Not established by this review

 - Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md)
 - Read the pinned source and its licence, then configure an explicitly bounded host context.
- Check the original display-style name and optional color/emoji/vibe metadata against the installed host requirements before loading a working copy. Current Claude Code documentation says unknown frontmatter fields are ignored; it does not establish a need to rewrite these names. Keep the archived/downloaded original unchanged.
- Review the current scanner/broker documentation, use placeholder examples and separately authorize rotation or history changes with a tested recovery plan.
- Supply redacted credential inventory, workload ownership and provider-specific revocation procedures.

### Before you start

 - Redacted inventory and workload owners
- Selected scanner and credential broker
- Authorized provider access only when executing

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated agent profile

 - No tools allowlist is declared. Claude Code can inherit or expose the host’s available tools by default; restrict file, shell and network access in the host.

### Cost model

The definition has the stated open-source licence. Model/host usage and any connected service or execution environment can incur separate costs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream agent definition ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md Supports: Workflow, inputs, outputs and stated boundaries
- [Applicable licence ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE Supports: Redistribution and attribution
- [Host configuration and tool inheritance ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host loading and effective permission boundaries

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Active Directory security posture reviewer ↗ An AD review profile tracing privilege, delegation, protocol and service-account risks into a remediation plan.](/agents/voltagent-ad-security-reviewer/)[### PowerShell automation hardening reviewer ↗ A PowerShell security profile for remoting boundaries, credential handling and sanitized operational logs.](/agents/voltagent-powershell-security-hardening/)[### Agent SDK verifier (Python) ↗ Checks a Python Claude Agent SDK app for SDK usage, environment setup and secret handling, and reports PASS, PASS WITH WARNINGS or FAIL.](/agents/anthropic-agent-sdk-verifier-py/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
