Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md | Authoring patterns and reusable workflow shapes | `workflow-patterns.md` |
Security audit
Security checks for vulnerabilities and agentic risk
This GitHub Actions skill is transparent and scoped to workflow design, debugging, hardening, and release guidance, with disclosed local notes and user-controlled GitHub access.
Install this if you want help with GitHub Actions workflows and are comfortable with local repo-context notes. Confirm before allowing workflow edits, live GitHub API actions, release changes, or deployment-affecting operations, and do not paste tokens or cloud keys into chat.
Referenced artifact was not completely inspected
| Authoring patterns and reusable workflow shapes | `workflow-patterns.md` |
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- GitHub repository access if the user wants live run inspection or workflow changes
- Deployment credentials only through GitHub-managed secrets, environments, or OIDC
Never ask the user to paste personal access tokens, cloud keys, or private signing material into chat.
## CI/CD Examples
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- GitHub repository access if the user wants live run inspection or workflow changes
- Deployment credentials only through GitHub-managed secrets, environments, or OIDC
Never ask the user to paste personal access tokens, cloud keys, or private signing material into chat.
## CI/CD Examples
Referenced artifact was not completely inspected
- modify its own `SKILL.md`
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- GitHub repository access if the user wants live run inspection or workflow changes
- Deployment credentials only through GitHub-managed secrets, environments, or OIDC
Never ask the user to paste personal access tokens, cloud keys, or private signing material into chat.
## CI/CD Examples
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- structures safe release and deployment automation
This skill NEVER:
- assume write access to repositories or environments without confirmation
- suggest secret exfiltration, masking bypasses, or hidden credential handling
- normalize production deployment from untrusted pull request contexts
No suspicious patterns detected.