Security audit
Security checks for vulnerabilities and agentic risk
This skill is a clearly scoped PoYo FLUX Dev API helper that sends only user-approved image-generation payloads to the documented PoYo endpoint.
Install only if you intend to use PoYo's FLUX Dev API. Treat POYO_API_KEY as a server-side secret, review payload JSON before submission, and avoid sending confidential prompts, private image URLs, or private callback URLs unless you trust PoYo and the callback receiver.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Content-Type: application/json
Get API keys from <https://poyo.ai/dashboard/api-key>. Use the server-side `POYO_API_KEY` environment variable.
## Model
The skill describes shell execution and network/secret usage, but it does not declare an enforceable tool scope such as explicit permissions or allowed-tools. That creates a policy gap where an agent runtime may permit broader shell behavior than the prose intends, increasing the chance of unintended command execution or access beyond the stated boundary.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer YOUR_API_KEY" \
--header "Content-Type: application/json" \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
This script performs a network POST request using the contents of the provided payload file and an authorization token from an environment variable, but the file contains no comment, echo message, or other user-facing disclosure that data will be sent to an external service. For code files, network transmission of user or system data should include some visible warning unless already documented elsewhere in the skill description, which is not present in this file.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
: "${POYO_API_KEY:?POYO_API_KEY is required}"
curl --fail-with-body --request POST \
--url "https://api.poyo.ai/api/generate/submit" \
--header "Authorization: Bearer ${POYO_API_KEY}" \
--header "Content-Type: application/json" \
--data @"$1"