agent-identity-engineer

Design workload identity, authorization, and audit architecture for AI-agent principals on Kubernetes.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agent-identity-engineer-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-identity-engineer
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/adp-enablement/skills/agent-identity-engineer
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agent-identity-engineer-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and automation often run on static API keys, shared service accounts, and over-permissive roles, making their actions unattributable, over-privileged, and unauditable. This Skill replaces that sprawl with an identity architecture built on ephemeral, attested, per-task credentials. ## Core Features & Use Cases - Identity stack design: Architect workload identity using Kubernetes projected service-account tokens, OIDC federation to cloud IAM, SPIFFE/SPIRE for multi-cluster estates, OAuth2 client credentials for agent-to-API calls, and mTLS with JWT claims propagation. - Scored maturity checklist: Assess the current estate against a 10-item checklist (no standing secrets, TTL-bounded credentials, per-task session identities, unified audit plane) scored 0-2 each and reported as n/20. - Authorization and audit design: Define platform-operation scope vocabularies, task-class-to-scope policy matrices, human gates for high-risk actions, and a unified human-plus-machine audit event schema with on-behalf-of chains. - Use Case: A platform team discovers agents sharing one broad service account with static keys in repos. Use this Skill to inventory principals, score the checklist, and produce an identity architecture brief with a phased migration sequence. ## Quick Start Use the agent-identity-engineer skill to inventory our agent credentials, score the identity checklist, and design a workload identity architecture for our Kubernetes platform.

Frequently Asked Questions about agent-identity-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I eliminate static API keys for AI agents on Kubernetes?

Replace static keys with projected service-account tokens that are audience-bound, time-bound, and pod-bound, then federate the cluster issuer to cloud IAM via OIDC so pods assume cloud roles with zero stored keys. Agents authenticate to APIs using OAuth2 client credentials with short-lived scoped tokens.

When should I use SPIFFE/SPIRE for workload identity?

Adopt SPIFFE/SPIRE when identity must span multiple clusters, clouds, or non-Kubernetes runtimes, since it issues SVIDs from attested node and workload selectors. For a single managed cluster with OIDC federation, it adds complexity without payoff.

How do I prevent confused deputy attacks in agent platforms?

Propagate the original principal in verified JWT claims so downstream services authorize on who is really asking, and issue per-agent per-task session identities rather than one shared service account. Scoping must happen at credential issuance, not internal filtering by gateways.

Does just-in-time approval work for automated agent workflows?

Per-action human approval stalls agent loops, so approval moves up a level: humans approve the policy mapping task classes to scopes, and agents receive per-task scoped credentials automatically. Only high-risk class-4 actions page a human.

What are the limitations of Vault-style secret management for agents?

Vault dynamic secrets and rotation are a transitional improvement over static credentials, but they still distribute strings that can be copied or leaked. The target end state is credential issuance from attested identity, not better distribution of secrets.