Caveat verdict

github-flow

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

GitHub issue and PR workflow automation with explicit safety guards including push rejection, PII sanitization, and main branch push restriction; no external data exfiltration or suspicious behavior.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

25
security
70
transparency
70
maintenance

Findings (5)

Pattern match critical

Possible hardcoded credential

dependencies.md · code · TOKEN="$(gh auth token --user <account>)

Pattern match critical

Pipe to python — executes piped content as Python code

pr.md · code · | python3

Pattern match medium

Instructs covert action — may act without user awareness

pr.md · prose · downgraded · silently

Pattern match low

Popular HTTP library — network access

merge.md · prose · downgraded · got

Pattern match low

References agent configuration files

plan-to-issue.md · prose · downgraded · CLAUDE.md

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API