Skills jeo
๐ฆ
jeo
v1.3.1 Content revision r1 Critical โ๏ธ External commands๐ Network access๐ Filesystem access๐ Env variables
Coordinate AI Agent Workflows with JEO
Complex AI coding sessions need consistent planning, verification, and handoff controls. JEO provides a cross-tool workflow for plan review, execution, UI feedback, and cleanup.
Supports: Claude Codex Code(CC)
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "jeo" from https://skillstore.io/skills/supercent-io-jeo.md and its manifest at https://skillstore.io/api/skills/supercent-io-jeo/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "jeo". Plan a login form update with JEO.
Expected outcome:
- The workflow enters PLAN phase and records the task state.
- A plan review gate is prepared before implementation begins.
- Execution waits for approval or feedback before moving forward.
Using "jeo". Use JEO to verify a dashboard change.
Expected outcome:
- The implementation is checked with browser verification tools.
- The result includes observed UI state and remaining issues.
- Cleanup guidance is provided after verification finishes.
Using "jeo". Run annotate mode after I submit UI feedback.
Expected outcome:
- Submitted annotations are listed and acknowledged.
- Each fix is applied, then marked resolved with a short summary.
- The loop stops when no submitted annotations remain.
Security Audit
Criticalv5 โข 7/9/2026 Open versioned report
The audit confirms serious install and persistence risks, including a remote installer executed through bash, user-level AI tool hooks, and automatic project source modification. Many markdown, localhost, and status-check matches were false positives, but the remaining confirmed behavior is enough to require manual review before publishing. No direct credential exfiltration intent was found. Static review was capped at 400/850 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
19
Files scanned
5,560
Lines analyzed
80
Review items
0
False positives ignored
Confirmed security concerns (6)
Critical
Pipe to shell pattern
if run "curl -fsSL https://plannotator.ai/install.sh | bash"; then
This line downloads a remote installer and executes it with bash through the installer helper. That pattern gives remote content immediate code execution during installation.
Critical
[HEURISTIC] DANGEROUS COMBINATION: Code execution + Network + Credential access
This combination is common in credential stealers and RATs
The combination is present through installers, subprocess hooks, local HTTP calls, and user configuration access. I did not find credential exfiltration intent, but the combined capability is a real marketplace risk.
Critical
Prompt Injection Attempt Detected
SKILL.md tells agents, "The following are commands, not descriptions. Execute them in order," and setup-codex.sh installs a prompt that says, "You are now operating in JEO mode." This attempts to steer host-agent behavior and should be treated as untrusted control text.
The files contain direct imperative control text that tells the agent to change mode, execute steps, and continue without user confirmation. This matches the prompt-injection patterns specified for this audit.
High
[HEURISTIC] SUSPICIOUS COMBINATION: Filesystem + Credentials + Network
This combination could indicate credential harvesting and exfiltration
The skill writes user-level AI tool configs and registers network-backed MCP or local HTTP workflows. The intent appears orchestration, but persistent config plus network access is a real risk.
High
Persistent User-Level Hook Installation
Setup scripts register hooks and MCP servers in user-level Claude, Codex, and Gemini configuration. Those hooks can run JEO scripts on future agent events outside the original installation command.
The setup scripts explicitly write hook commands and MCP server definitions to hidden user configuration files. The behavior is documented and implemented in multiple platform installers.
High
Automatic Project Source Modification
The agentation helper installs a package and rewrites a discovered React entry point to mount its component. This can change application source without a user-reviewed diff or project-specific allowlist.
The helper opens and writes the entry file, while SKILL.md states the package and component are auto-installed and auto-injected. This is a clear intent-level project modification risk.
Capability review items (80)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Critical
Hardcoded URL
if run "curl -fsSL https://plannotator.ai/install.sh | bash"; then
This URL is used to download and execute a remote plannotator installer. Remote executable install sources require pinning and verification.
High
Hidden file in home directory
# Configures: omc plugin, plannotator hook, agentation MCP, jeo workflow in ~/.claude/settings.json
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
# โโ 2. Configure ~/.claude/settings.json โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
info "Configuring ~/.claude/settings.json..."
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
settings_path = os.path.expanduser("~/.claude/settings.json")
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
# Configures: developer_instructions + agentation MCP in ~/.codex/config.toml + /prompts:jeo
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
# โโ 2. Configure ~/.codex/config.toml โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
info "Configuring ~/.codex/config.toml..."
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
config_path = os.path.expanduser("~/.codex/config.toml")
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
ok "JEO developer_instructions synced in ~/.codex/config.toml"
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
# discovery of plannotator when it is installed in ~/.local/bin.
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
os.path.expanduser("~/.codex/skills/jeo/scripts/plannotator-plan-loop.sh"),
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
os.path.expanduser("~/.agent-skills/jeo/scripts/plannotator-plan-loop.sh"),
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
config_path = os.path.expanduser("~/.codex/config.toml")
This setup script targets user-level hidden configuration paths and registers hooks or MCP settings. Persistent changes under home directories are security-relevant for an installable skill.
High
Hidden file in home directory
**Config file**: `~/.claude/settings.json`
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
"command": "python3 ~/.agent-skills/jeo/scripts/claude-plan-gate.py",
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
**agentation MCP config** (`~/.claude/settings.json` or `.claude/mcp.json`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
"command": "python3 ~/.agent-skills/jeo/scripts/claude-agentation-submit-hook.py",
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
`bash ~/.agent-skills/jeo/scripts/setup-claude.sh` migrates stale `~/.agent-skills/omg/...` hook pat
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
# - developer_instructions: ~/.codex/config.toml
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
# - prompt file: ~/.codex/prompts/jeo.md
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
# - notify hook: ~/.codex/hooks/jeo-notify.py
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
**agentation MCP config** (`~/.codex/config.toml`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
**notify hook** (`~/.codex/hooks/jeo-notify.py`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
**`~/.codex/config.toml`** config:
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
notify = ["python3", "~/.codex/hooks/jeo-notify.py"]
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
# - AfterAgent backup hook: ~/.gemini/hooks/jeo-plannotator.sh
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
# - Instructions (MANDATORY loop): ~/.gemini/GEMINI.md
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
**AfterAgent backup hook** (`~/.gemini/settings.json`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file in home directory
"command": "bash ~/.gemini/hooks/jeo-plannotator.sh",
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Python subprocess.run
proc = subprocess.run(
The Claude hook directly launches the external plannotator binary during plan review. This is intended behavior, but it creates automatic command execution from a persistent hook.
High
Python subprocess.run
result = subprocess.run(
The generated Codex hook runs bash or plannotator from a notify path. This is an intended orchestration flow, but it is persistent external command execution.
High
Python subprocess.run
subprocess.run(["plannotator"], input=payload, stdout=f, stderr=f, text=True, env=get_plannotator_en
The generated Codex hook runs bash or plannotator from a notify path. This is an intended orchestration flow, but it is persistent external command execution.
High
Python subprocess.run
' subprocess.run(["python3", h, raw], check=False)\n'
The dispatcher executes registered hook scripts from a user-level registry. That creates a persistent fan-out execution path for future Codex notifications.
High
Hidden file access
**Config file**: `~/.claude/settings.json`
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
"command": "python3 ~/.agent-skills/jeo/scripts/claude-plan-gate.py",
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
**agentation MCP config** (`~/.claude/settings.json` or `.claude/mcp.json`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
"command": "python3 ~/.agent-skills/jeo/scripts/claude-agentation-submit-hook.py",
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
`bash ~/.agent-skills/jeo/scripts/setup-claude.sh` migrates stale `~/.agent-skills/omg/...` hook pat
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
# - developer_instructions: ~/.codex/config.toml
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
# - prompt file: ~/.codex/prompts/jeo.md
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
# - notify hook: ~/.codex/hooks/jeo-notify.py
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Hidden file access
**agentation MCP config** (`~/.codex/config.toml`):
This documentation instructs users to configure persistent hooks in hidden AI tool directories. It is prose, but it describes the same durable execution path implemented by the setup scripts.
High
Python file write/append
with open(entry_path, 'w', encoding='utf-8') as f:
This script rewrites the discovered React entry point to inject the Agentation component. Automatic source modification in a user project is security-relevant.
High
Python file write/append
with open(settings_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(config_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(config_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(feedback_file, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(dispatcher_path, "w") as _f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(registry_path, "w") as _f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(config_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(settings_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(settings_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(settings_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python file write/append
with open(settings_path, "w") as f:
This setup script writes user-level tool configuration, hook files, or prompt files. These writes can persist behavior across future AI tool sessions.
High
Python os file operations
os.makedirs(os.path.dirname(settings_path), exist_ok=True)
The os operations create user-level configuration or hook directories for AI tools. This supports persistence and deserves review.
High
Python os file operations
os.makedirs(feedback_dir, exist_ok=True)
The os operations create user-level configuration or hook directories for AI tools. This supports persistence and deserves review.
High
Python os file operations
os.makedirs(runtime_home, exist_ok=True)
The os operations create user-level configuration or hook directories for AI tools. This supports persistence and deserves review.
High
Python os file operations
os.makedirs(os.path.dirname(dispatcher_path), exist_ok=True)
The os operations create user-level configuration or hook directories for AI tools. This supports persistence and deserves review.
Medium
Temp directory access
RUNTIME_ROOT="/tmp/jeo-opencode-${SESSION_KEY}"
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
# bash ${JEO_SKILL_DIR}/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
bash .agent-skills/jeo/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt 3
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
3. Read /tmp/plannotator_feedback.txt
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
bash .agent-skills/jeo/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt 3
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
d = json.load(open('/tmp/plannotator_feedback.txt'))
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
" && echo "PLAN_APPROVED โ proceed to EXECUTE" || cat /tmp/plannotator_feedback.txt
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
feedback_dir = f"/tmp/jeo-{_session_key}"
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
runtime_home = f"/tmp/jeo-{_session_key}/.plannotator"
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
echo " writes to: /tmp/plannotator_feedback.txt"
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
# bash .agent-skills/jeo/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt 3
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
LOCK_FILE="/tmp/jeo-plannotator-direct.lock"
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
bash "$LOOP_SCRIPT" "$PLAN_FILE" /tmp/plannotator_feedback.txt 3
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
PLANNOTATOR_RUNTIME_HOME="/tmp/jeo-$(python3 -c "import hashlib,os; print(f'/tmp/jeo-{hashlib.md5(os
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
" "$PLAN_FILE" | env HOME="$PLANNOTATOR_RUNTIME_HOME" PLANNOTATOR_HOME="$PLANNOTATOR_RUNTIME_HOME" p
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
bash .agent-skills/jeo/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt 3
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
3. /tmp/plannotator_feedback.txt ์ฝ๊ธฐ
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp directory access
"bash .agent-skills/jeo/scripts/plannotator-plan-loop.sh plan.md /tmp/plannotator_feedback.txt 3. "
The scripts use predictable temporary paths for plannotator feedback, locks, or runtime homes. This is common tooling behavior but can create collision or tampering risk.
Medium
Temp file creation
import tempfile
The hook creates a predictable temp lock file for concurrency control. This is not malicious, but lock files in shared temp space can be tampered with.
Medium
Temp file creation
_LOCK_FILE = Path(tempfile.gettempdir()) / "jeo-plannotator-claude-gate.lock"
The hook creates a predictable temp lock file for concurrency control. This is not malicious, but lock files in shared temp space can be tampered with.
Low
Python environment access
env = os.environ.copy()
The generated hook copies the full process environment before launching plannotator. This is normal subprocess behavior, but it can expose environment variables to child tools.
Risk Factors
โ๏ธ External commands (50)
opencode.json.jeo.bak:18 scripts/check-status.sh:176 scripts/check-status.sh:182 scripts/check-status.sh:183 scripts/check-status.sh:184 scripts/check-status.sh:185 scripts/check-status.sh:186 scripts/check-status.sh:187 scripts/check-status.sh:188 scripts/check-status.sh:257 scripts/claude-agentation-submit-hook.py:34 scripts/claude-agentation-submit-hook.py:100 scripts/claude-plan-gate.py:257 scripts/claude-plan-gate.py:50 scripts/claude-stop-continuation.py:34 scripts/ensure-agentation.sh:13 scripts/ensure-agentation.sh:52 scripts/ensure-agentation.sh:151 scripts/ensure-agentation.sh:234 scripts/ensure-agentation.sh:251 scripts/ensure-plannotator.sh:6 scripts/ensure-plannotator.sh:7 scripts/ensure-plannotator.sh:8 scripts/ensure-plannotator.sh:32 scripts/ensure-plannotator.sh:56 scripts/install.sh:8 scripts/install.sh:9 scripts/install.sh:10 scripts/install.sh:90 scripts/install.sh:92 scripts/plannotator-plan-loop.sh:83 scripts/plannotator-plan-loop.sh:121 scripts/plannotator-plan-loop.sh:184 scripts/plannotator-plan-loop.sh:7 scripts/plannotator-plan-loop.sh:39-41 scripts/plannotator-plan-loop.sh:50 scripts/plannotator-plan-loop.sh:58 scripts/plannotator-plan-loop.sh:222 scripts/run-opencode-safe.sh:12 scripts/setup-claude.sh:17 scripts/setup-claude.sh:43 scripts/setup-codex.sh:457 scripts/setup-codex.sh:477 scripts/setup-codex.sh:572 scripts/setup-codex.sh:165 scripts/setup-codex.sh:167 scripts/setup-codex.sh:172 scripts/setup-codex.sh:174 scripts/setup-codex.sh:175 scripts/setup-codex.sh:177
๐ Network access (50)
opencode.json.jeo.bak:2 opencode.json.jeo.bak:18 references/FLOW.md:114 references/FLOW.md:344 references/FLOW.md:347 references/FLOW.md:351 references/FLOW.md:458 scripts/claude-agentation-submit-hook.py:15 scripts/claude-agentation-submit-hook.py:90 scripts/claude-agentation-submit-hook.py:90 scripts/claude-plan-gate.py:214 scripts/ensure-agentation.sh:17 scripts/install.sh:114 scripts/install.sh:134 scripts/install.sh:146 scripts/install.sh:165 scripts/install.sh:169 scripts/install.sh:223 scripts/plannotator-plan-loop.sh:286 scripts/plannotator-plan-loop.sh:291 scripts/plannotator-plan-loop.sh:303 scripts/plannotator-plan-loop.sh:328 scripts/plannotator-plan-loop.sh:338 scripts/setup-claude.sh:29 scripts/setup-claude.sh:145 scripts/setup-claude.sh:164 scripts/setup-claude.sh:226 scripts/setup-codex.sh:283 scripts/setup-codex.sh:500 scripts/setup-codex.sh:197 scripts/setup-codex.sh:237 scripts/setup-codex.sh:498 scripts/setup-gemini.sh:144 scripts/setup-gemini.sh:308 scripts/setup-gemini.sh:319 scripts/setup-opencode.sh:75 SKILL.md:409 SKILL.md:421 SKILL.md:423 SKILL.md:452 SKILL.md:502 SKILL.md:508 SKILL.md:531 SKILL.md:664 SKILL.md:667 SKILL.md:671 SKILL.md:685 SKILL.md:690 SKILL.md:865 SKILL.md:870
๐ Filesystem access (50)
opencode.json.jeo.bak:18 opencode.json.jeo.bak:18 references/FLOW.md:117 references/FLOW.md:119 references/FLOW.md:210 references/FLOW.md:211 references/FLOW.md:224 references/FLOW.md:225 references/FLOW.md:435 references/FLOW.md:462 references/FLOW.md:197 references/FLOW.md:210 references/FLOW.md:211 references/FLOW.md:224 references/FLOW.md:225 references/FLOW.md:435 references/FLOW.md:462 references/FLOW.md:410 scripts/check-status.sh:75 scripts/check-status.sh:99 scripts/check-status.sh:102 scripts/check-status.sh:140 scripts/check-status.sh:151 scripts/check-status.sh:63 scripts/check-status.sh:64 scripts/check-status.sh:75 scripts/check-status.sh:88 scripts/check-status.sh:93 scripts/check-status.sh:98 scripts/check-status.sh:99 scripts/check-status.sh:102 scripts/check-status.sh:106 scripts/check-status.sh:124 scripts/check-status.sh:129 scripts/check-status.sh:134 scripts/check-status.sh:140 scripts/check-status.sh:144 scripts/check-status.sh:145 scripts/check-status.sh:151 scripts/check-status.sh:153 scripts/check-status.sh:154 scripts/check-status.sh:162 scripts/check-status.sh:177 scripts/check-status.sh:207 scripts/check-status.sh:21 scripts/check-status.sh:30 scripts/check-status.sh:64 scripts/check-status.sh:80 scripts/check-status.sh:88 scripts/check-status.sh:93
๐ Env variables (19)
scripts/check-status.sh:211 scripts/claude-plan-gate.py:43 scripts/ensure-agentation.sh:167 scripts/ensure-agentation.sh:167 scripts/plannotator-plan-loop.sh:94 scripts/plannotator-plan-loop.sh:139 scripts/plannotator-plan-loop.sh:151 scripts/plannotator-plan-loop.sh:152 scripts/plannotator-plan-loop.sh:153 scripts/plannotator-plan-loop.sh:154 scripts/plannotator-plan-loop.sh:197 scripts/setup-claude.sh:60 scripts/setup-codex.sh:349 scripts/setup-gemini.sh:343 scripts/setup-gemini.sh:344 scripts/setup-opencode.sh:62 scripts/setup-opencode.sh:102 scripts/worktree-cleanup.sh:154 SKILL.md:378
Detected Patterns
Pipe to shell pattern[HEURISTIC] DANGEROUS COMBINATION: Code execution + Network + Credential access
Audited by: codex View Audit History โ
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/supercent-io-jeo/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/supercent-io-jeo?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/supercent-io-jeo?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supercent-io-jeo/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/supercent-io-jeo.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
supercent-io. (2026). jeo security audit report (audit version 5) [Author version 1.3.1]. Skillstore. https://skillstore.io/skills/supercent-io-jeo/audits/5BibTeX citation
@techreport{supercent-io-supercent-io-jeo-2026,
author = {supercent-io},
title = {jeo security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/supercent-io-jeo/audits/5},
note = {Author version 1.3.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "jeo security audit report (audit version 5)"
version: "1.3.1"
type: report
authors:
- name: "supercent-io"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/supercent-io-jeo/audits/5"
identifiers:
- type: other
value: "skillstore:supercent-io-jeo:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 64
Architecture
100
Maintainability
85
Content
69
Community
78
Spec Compliance
What You Can Build
Structure a coding workflow
Create a plan gate, execution phase, verification step, and cleanup step for a coding task.
Review browser UI changes
Run browser verification and collect submitted UI annotations before resolving feedback.
Standardize agent setup
Install similar orchestration behavior across several AI coding tools.
Try These Prompts
Plan a small task
Use JEO to plan this task first, then wait for plan approval before implementation: <task>.
Verify a UI change
Use JEO to implement this UI change, verify the page in a browser, and summarize the visible result.
Process UI annotations
Use JEO annotate mode after I submit UI annotations. Acknowledge each item, apply fixes, and report what changed.
Audit the workflow setup
Review the JEO setup for this repository. Identify which hooks, prompts, local services, and cleanup steps are active.
Best Practices
- Run setup scripts with dry-run first and review every configuration change.
- Use JEO only in trusted repositories where local hooks are expected.
- Keep localhost services private and stop them when the workflow ends.
Avoid
- Do not run the full installer in an untrusted repository.
- Do not let the skill auto-modify application entry points without reviewing the diff.
- Do not treat generated plan approval as a replacement for human review on sensitive work.
Frequently Asked Questions
What does JEO coordinate?
It coordinates planning, execution, browser verification, UI annotation review, and cleanup across several AI coding tools.
Which tools does it support?
The report lists support for Claude, Claude Code, and Codex, with files also describing Gemini CLI and OpenCode setup.
Does it install external tools?
Yes. Several setup paths use npm, npx, plugin commands, or installer scripts for external components.
Does it change user configuration?
Yes. Setup scripts can write Claude, Codex, Gemini, and OpenCode configuration files in the user home directory.
Does it need network access?
Some flows use local HTTP services, package registries, plugin marketplaces, or remote installer URLs.
Is it safe for automatic marketplace install?
No. The audit identifies persistent hooks, remote installers, and automatic source modification that require manual review.
Developer Details
Author
supercent-ioLicense
MIT
Author version
v1.3.1
Skillstore revision
r1
Ref
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Maintenance freshness
7/18/2026
Usage
7 downloads ยท 130 views
File structure
๐ references/
๐ FLOW.md
๐ PLANNOTATOR_RELIABILITY_CONSENSUS_2026-03-06.md
๐ scripts/
๐ check-status.sh
๐ claude-agentation-submit-hook.py
๐ claude-plan-gate.py
๐ claude-stop-continuation.py
๐ ensure-agentation.sh
๐ install.sh
๐ run-opencode-safe.sh
๐ setup-claude.sh
๐ setup-codex.sh
๐ setup-gemini.sh
๐ setup-opencode.sh
๐ worktree-cleanup.sh
๐ SKILL.md
๐ SKILL.toon