Information Disclosure
DevOps & Securityinformation-disclosureInformation Disclosure is an Agent Skill for devops & security published in the kubernetes-sigs/kueue repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Flag information-disclosure patterns — full-object logging, request echoing, credentials in status/annotations, kubeconfig logging, secret-bearing status (CWE-200, CWE-522, CWE-532, CWE-552).
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/kubernetes-sigs/kueue/blob/HEAD/cmd/experimental/skills/reviewer/security/information-disclosure/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/information-disclosure, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Information Disclosure (CWE-200, CWE-522, CWE-532, CWE-552)
- Full Kubernetes objects logged with
%+v/%#v. Required:klog.KObj(obj)plus structured key/value pairs. - Webhook responses, events, or status fields that echo request bodies, stack traces, or credential-bearing fields.
- Credentials or tokens persisted in annotations, labels, env vars, or status — credentials belong in mounted Secrets.
- kubeconfigs logged, echoed in status, or written with
insecure-skip-tls-verify: true. - Visibility-API or metrics queries that widen results past the caller's namespace/queue.
- Secret-bearing data written to
.status— status updates are at-least-once, so every retry leaks.