T09 · Insecure Skill Coding Practices
- Location
SKILL.md:190- Finding
Private repository credential remains accessible to deployed application code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a transparent AgentsPodium deployment guide, but it deserves review because private repository tokens are stored for rebuilds and exposed inside the running pod.
Install or use this only if you are comfortable sending deployment configuration to AgentsPodium. For private repositories, use a short-lived, read-only token scoped to one repository, rotate it after deployment if possible, and do not deploy code or dependencies you do not trust while that token is available in the pod environment.
SKILL.md:190Private repository credential remains accessible to deployed application code
SKILL.md:77Unpinned package execution through npx during deployment
The description says to use the skill when asked to 'ship an app somewhere' or 'move a site off Netlify or Vercel,' which is broad natural language that overlaps with many generic deployment requests. It does not clearly constrain invocation to AgentsPodium-specific deployments or provide exclusion conditions, increasing the risk of unintended activation.
This skill instructs sending sensitive deployment data to an external service, including repository URLs, environment variables, and potentially repoToken for private repositories. External transmission is expected for a deployment skill, but it is still security-relevant because the deployed code runs in the same pod and the document explicitly states the repo token lives in the pod environment, meaning untrusted application code could read and misuse it.
a self-hosted Forgejo:
curl -s -X POST https://agentspodium.com/api/agents \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{
"engine": "app",
"tier": "small",
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Listing agents with an API key transmits and returns potentially sensitive metadata to an external service, including agent IDs, names, endpoint URLs, and repository information visible to that key. In context this is normal platform usage, but it remains a real security-sensitive operation because compromise or overuse of the key exposes infrastructure inventory and app details that aid follow-on attacks.
If you do not have the id, list what the key can see:
curl -s https://agentspodium.com/api/agents -H "Authorization: Bearer $TOKEN"
# {"agents":[{"id":"agt_…","name":"hq-app","engine":"app","status":"running",
# "endpointUrl":"https://…","app":{"repo":"…","branch":"main",…}}]}
The manifest frames this skill as deploying a project from a git repository onto AgentsPodium. In the documentation, however, it expands into general instance administration and billing-related operations by pointing users to status, liveness, usage, term, pause/resume/delete/export, and payment endpoints, which exceed the narrow semantic scope of 'deploy an app.'
The manifest describes a deployment skill focused on shipping apps from git repositories. Mentioning an alternate mailbox-based auth flow introduces account authentication behavior that is not necessary to understand or perform the core deployment task and broadens the apparent scope of the skill.
No suspicious patterns detected.