codex-thread-heartbeat
Inspect and manage guarded Codex App-native or launchd heartbeats for Codex main control threads. Use when the user wants Codex to periodically continue a specific thread only when it is idle, avoid interrupting active work, keep App-visible interactions, inspect thread status, or enable/disable project autopilot heartbeats.
67
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required runtime workflow uses the local `state_5.sqlite` rollout log parsing (reading `rollout_path` lines) to decide/format the heartbeat, and that rollout JSONL is outsider-authored model-generated content that can contain arbitrary free text/prompt-injection strings; the script ingests it as readable JSON fields and includes derived text in the LLM-bound “message”/“input” path when sending `turn/start` (or `codex exec resume` with `args.message`).
- Repository
huangruiteng/CS-Notes
- Revision
0825d79
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.