Secrets and CI permissions audit
Review exposed-secret indicators and workflow permissions without disclosing credentials.
Customize the recipe
0/1500 characters
Prompt preview
# Secrets and CI permissions audit Review exposed-secret indicators and workflow permissions without disclosing credentials. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Agentic Actions Auditor](https://github.com/trailofbits/skills/blob/main/plugins/agentic-actions-auditor/skills/agentic-actions-auditor/SKILL.md) (Skill) — Reference the static review guidance for workflow permissions and untrusted inputs. - [Gitleaks](https://github.com/gitleaks/gitleaks) (Repository) — Review redacted secrets findings or run an existing offline scan against supplied source. - [OpenSSF Scorecard](https://github.com/ossf/scorecard) (Repository) — Review software supply-chain practices using available scorecard reports and repository configuration. ## Workflow Review supplied workflow files and redacted secret-scan findings. Map trust boundaries for job tokens, logs, artifacts, and untrusted inputs. Refer to potential credentials by file location and finding type and leave validation or rotation to the owner. ## Deliverable A redacted report covering credential exposure indicators and CI privilege risks. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Report secrets using masked indicators and avoid copying raw values. - [ ] Cite the workflow event, job, or specific configuration that supports each permission finding. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Agentic Actions Auditor
Reference the static review guidance for workflow permissions and untrusted inputs.
Upstream documents Claude Code.
8.3K GitHub stars on the source repository
Gitleaks
Review redacted secrets findings or run an existing offline scan against supplied source.
License · MIT
31.3K GitHub stars
OpenSSF Scorecard
Review software supply-chain practices using available scorecard reports and repository configuration.
License · Apache-2.0
5.9K GitHub stars