T09 · Insecure Skill Coding Practices
- Location
SKILL.md:94- Finding
Meta access tokens and application secrets are exposed through URL query strings and standard output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is for legitimate Facebook Page operations, but it handles powerful Page tokens and live public posting without enough safeguards.
Review this skill before installing if the Facebook Page is business-critical. Use least-privilege tokens, avoid running token-generation examples in logged or shared environments, redact API output, and require a manual confirmation before any live post, comment, reply, or browser-driven action.
SKILL.md:94Meta access tokens and application secrets are exposed through URL query strings and standard output
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Meaning of each config item:
- `FACEBOOK_PAGE_ID`: the numeric Facebook Page ID used in Graph API endpoints
- `FACEBOOK_PAGE_ACCESS_TOKEN`: the Page access token used to publish posts and test engagement actions
- `FACEBOOK_GRAPH_VERSION`: optional Graph API version pin, e.g. `v22.0`
Quick check:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Meaning of each config item:
- `FACEBOOK_PAGE_ID`: the numeric Facebook Page ID used in Graph API endpoints
- `FACEBOOK_PAGE_ACCESS_TOKEN`: the Page access token used to publish posts and test engagement actions
- `FACEBOOK_GRAPH_VERSION`: optional Graph API version pin, e.g. `v22.0`
Quick check:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Meaning of each config item:
- `FACEBOOK_PAGE_ID`: the numeric Facebook Page ID used in Graph API endpoints
- `FACEBOOK_PAGE_ACCESS_TOKEN`: the Page access token used to publish posts and test engagement actions
- `FACEBOOK_GRAPH_VERSION`: optional Graph API version pin, e.g. `v22.0`
Quick check:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `pages_manage_posts`
- `pages_manage_engagement`
- `pages_read_user_content` (recommended for comment-related workflows)
3. Generate a **short-lived User Access Token** for the Facebook account that manages the Page.
4. Exchange it for a **long-lived User Access Token**.
5. Use the long-lived user token to query Page accounts and retrieve the Page access token.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `pages_manage_posts`
- `pages_manage_engagement`
- `pages_read_user_content` (recommended for comment-related workflows)
3. Generate a **short-lived User Access Token** for the Facebook account that manages the Page.
4. Exchange it for a **long-lived User Access Token**.
5. Use the long-lived user token to query Page accounts and retrieve the Page access token.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `pages_manage_posts`
- `pages_manage_engagement`
- `pages_read_user_content` (recommended for comment-related workflows)
3. Generate a **short-lived User Access Token** for the Facebook account that manages the Page.
4. Exchange it for a **long-lived User Access Token**.
5. Use the long-lived user token to query Page accounts and retrieve the Page access token.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `pages_manage_posts`
- `pages_manage_engagement`
- `pages_read_user_content` (recommended for comment-related workflows)
3. Generate a **short-lived User Access Token** for the Facebook account that manages the Page.
4. Exchange it for a **long-lived User Access Token**.
5. Use the long-lived user token to query Page accounts and retrieve the Page access token.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- after adding new permissions, you often need to **re-generate the token**
- if the app is still in **Development mode**, some production behaviors may stay blocked
- the acting Facebook account must actually have the necessary Page role/permissions
- long-lived user tokens are typically around **60 days**, while Page access tokens obtained through them are usually the practical token used for Page posting workflows
- even a long-usable Page token can still stop working if the user changes password, removes app authorization, loses Page role access, or the app mode/permissions change
## Default execution policy
The configuration section instructs use of sensitive credentials such as FACEBOOK_PAGE_ACCESS_TOKEN without any warning about secure storage, redaction, or avoiding disclosure in logs and chat transcripts. Because the skill also includes diagnostic commands that print API responses, the absence of handling guidance increases the chance of accidental token exposure during normal use.
The skill explicitly automates live Facebook posting, commenting, replying, and browser fallback, but it does not require a clear pre-action confirmation that these actions will affect a real Page. This creates a meaningful risk of unintended public actions, especially because the default policy encourages direct execution paths rather than an explicit human approval checkpoint.