SECURITY OPERATIONS / Agency Agents community
Credential lifecycle and leak-response planner
A credential-lifecycle profile connecting detection, ownership, provider revocation and controlled rotation.
“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.”
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.
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.
- 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
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/security/security-secrets-credential-engineer.md
Supports: Workflow, inputs, outputs and stated boundaries
- Applicable licence ↗Checked
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Redistribution and attribution
https://code.claude.com/docs/en/sub-agents.md
Supports: Host loading and effective permission boundaries