Caveat verdict

afrexai-api-architect

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

This is an API design methodology guide; network and credential capabilities are consistent with legitimate API development workflows, and the content contains only documentation and best-practice templates with no malicious patterns.

⚠ 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.

50
security
50
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (1)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="your_bearer_token

Permissions & capabilities

No declared permissions — minimal attack surface.

network_innetwork_outcredential_accesspackage_install

Is this flag fair?

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