📦
prompt-repetition
82تحسين دقة النماذج خفيفة الوزن
قد تفوّت النماذج خفيفة الوزن السياق عندما تأتي الأسئلة بعد معلومات مهمة. تكرر هذه المهارة المطالبات المناسبة مع ضوابط حماية لتحسين الدقة في مهام مختارة.
الإنتاجية عرض
المهارات jeo
📦
jeo
v1.3.1 مراجعة المحتوى r1 حرج ⚙️ الأوامر الخارجية🌐 الوصول إلى الشبكة📁 الوصول إلى نظام الملفات🔑 متغيرات البيئة
نسّق سير عمل وكلاء الذكاء الاصطناعي باستخدام JEO
تحتاج جلسات البرمجة المعقدة باستخدام الذكاء الاصطناعي إلى تخطيط وتحقق وضوابط تسليم متسقة. يوفر JEO سير عمل عابرًا للأدوات لمراجعة الخطة والتنفيذ وملاحظات UI والتنظيف.
يدعم: Claude Codex Code(CC)
لا تثبّت هذا Skill تلقائيًا.
تتطلب السياسة المعتمدة مراجعة المشغّل قبل أي إجراء تثبيت.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
طلب الوكيل
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.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "jeo". خطط لتحديث نموذج تسجيل الدخول باستخدام JEO.
النتيجة المتوقعة:
- يدخل سير العمل مرحلة PLAN ويسجل حالة المهمة.
- يتم إعداد بوابة مراجعة الخطة قبل بدء التنفيذ.
- ينتظر التنفيذ الموافقة أو الملاحظات قبل المتابعة.
جارٍ استخدام "jeo". استخدم JEO للتحقق من تغيير في لوحة معلومات.
النتيجة المتوقعة:
- يتم فحص التنفيذ باستخدام أدوات التحقق عبر المتصفح.
- تتضمن النتيجة حالة UI المرصودة والمشكلات المتبقية.
- يتم توفير إرشادات التنظيف بعد انتهاء التحقق.
جارٍ استخدام "jeo". شغّل وضع التعليق بعد أن أرسل ملاحظات UI.
النتيجة المتوقعة:
- يتم سرد التعليقات المقدمة والإقرار بها.
- يتم تطبيق كل إصلاح، ثم وسمه كمحلول مع ملخص قصير.
- تتوقف الحلقة عندما لا تبقى أي تعليقات مقدمة.
التدقيق الأمني
حرجv5 • ٩/٧/٢٠٢٦ فتح التقرير المرتبط بالإصدار
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
الملفات التي تم فحصها
5,560
الأسطر التي تم تحليلها
80
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة
مخاوف أمنية مؤكدة (6)
حرج
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.
حرج
[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.
حرج
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.
مرتفع
[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.
مرتفع
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.
مرتفع
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.
عناصر مراجعة القدرات (80)
هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.
حرج
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
منخفض
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.
عوامل الخطر
⚙️ الأوامر الخارجية (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
🌐 الوصول إلى الشبكة (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
📁 الوصول إلى نظام الملفات (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
🔑 متغيرات البيئة (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
الأنماط المكتشفة
Pipe to shell pattern[HEURISTIC] DANGEROUS COMBINATION: Code execution + Network + Credential access
دقّقه: codex عرض سجل التدقيق →
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/supercent-io-jeo/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/supercent-io-jeo?utm_source=security_passport_badge)شارة HTML
<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>بطاقة قابلة للتضمين
<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>الاستشهادات الأكاديمية (APA · BibTeX · CFF)
اقتباس APA
supercent-io. (2026). jeo security audit report (audit version 5) [Author version 1.3.1]. Skillstore. https://skillstore.io/skills/supercent-io-jeo/audits/5اقتباس BibTeX
@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
سبب هذا التقييم موثوقية الأدلة: متوسط 64
الهندسة المعمارية
100
قابلية الصيانة
85
المحتوى
69
المجتمع
78
الامتثال للمواصفات
ما الذي يمكنك بناؤه
هيكلة سير عمل برمجي
أنشئ بوابة خطة ومرحلة تنفيذ وخطوة تحقق وخطوة تنظيف لمهمة برمجية.
مراجعة تغييرات UI في المتصفح
شغّل التحقق عبر المتصفح واجمع تعليقات UI المقدمة قبل حل الملاحظات.
توحيد إعداد الوكلاء
ثبّت سلوك تنسيق مشابهًا عبر عدة أدوات برمجة بالذكاء الاصطناعي.
جرّب هذه الموجّهات
خطط لمهمة صغيرة
استخدم JEO للتخطيط لهذه المهمة أولًا، ثم انتظر الموافقة على الخطة قبل التنفيذ: <task>.
تحقق من تغيير في UI
استخدم JEO لتنفيذ هذا التغيير في UI، والتحقق من الصفحة في المتصفح، وتلخيص النتيجة المرئية.
معالجة تعليقات UI
استخدم وضع التعليق في JEO بعد أن أرسل تعليقات UI. أقرّ بكل عنصر، وطبّق الإصلاحات، وأبلغ عما تغيّر.
تدقيق إعداد سير العمل
راجع إعداد JEO لهذا المستودع. حدد الخطافات والموجهات والخدمات المحلية وخطوات التنظيف النشطة.
أفضل الممارسات
- شغّل نصوص الإعداد بوضع dry-run أولًا وراجع كل تغيير في الإعدادات.
- استخدم JEO فقط في المستودعات الموثوقة التي يُتوقع فيها وجود خطافات محلية.
- أبقِ خدمات localhost خاصة وأوقفها عند انتهاء سير العمل.
تجنب
- لا تشغّل المثبّت الكامل في مستودع غير موثوق.
- لا تسمح للمهارة بتعديل نقاط دخول التطبيق تلقائيًا من دون مراجعة diff.
- لا تعامل الموافقة المُنشأة على الخطة كبديل للمراجعة البشرية في الأعمال الحساسة.
الأسئلة المتكررة
ماذا ينسق JEO؟
ينسق التخطيط والتنفيذ والتحقق عبر المتصفح ومراجعة تعليقات UI والتنظيف عبر عدة أدوات برمجة بالذكاء الاصطناعي.
ما الأدوات التي يدعمها؟
يسرد التقرير دعم Claude وClaude Code وCodex، مع ملفات تصف أيضًا إعداد Gemini CLI وOpenCode.
هل يثبّت أدوات خارجية؟
نعم. تستخدم عدة مسارات إعداد npm أو npx أو أوامر الإضافات أو نصوص التثبيت للمكونات الخارجية.
هل يغيّر إعدادات المستخدم؟
نعم. يمكن لنصوص الإعداد كتابة ملفات إعداد Claude وCodex وGemini وOpenCode في دليل المنزل الخاص بالمستخدم.
هل يحتاج إلى وصول إلى الشبكة؟
تستخدم بعض التدفقات خدمات HTTP محلية أو سجلات حزم أو أسواق إضافات أو عناوين URL للتثبيت عن بُعد.
هل هو آمن للتثبيت التلقائي من السوق؟
لا. يحدد التدقيق الخطافات الدائمة والمثبتات عن بُعد وتعديل المصدر التلقائي التي تتطلب مراجعة يدوية.
تفاصيل المطور
المؤلف
supercent-ioالترخيص
MIT
إصدار المؤلف
v1.3.1
مراجعة Skillstore
r1
مرجع
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
حداثة الصيانة
١٨/٧/٢٠٢٦
الاستخدام
7 تنزيلات · 130 مشاهدات
بنية الملفات
المزيد من supercent-io
عرض الكل📦
api-design
80تصميم REST وGraphQL APIs بشكل أفضل
تحتاج فرق API إلى عقود متسقة قبل بدء التنفيذ. ترشد هذه المهارة تصميم الموارد، وتنسيقات الطلبات، والأخطاء، وإدارة الإصدارات، والتوثيق.
البرمجة والتطوير عرض
📦
code-refactoring
79إعادة هيكلة الكود بأمان
الكود المعقد يبطئ إجراء التغييرات ويزيد خطر الانحدارات. ترشد هذه المهارة إلى عمليات إعادة هيكلة تحافظ على السلوك باستخدام الاختبارات وأنماط الاستخراج وخطوات التحقق.
البرمجة والتطوير عرض
📦
user-guide-writing
79اكتب أدلة مستخدم واضحة
تحتاج الفرق إلى وثائق مستخدم تشرح المهام دون إرباك القراء. تنظّم هذه المهارة الأدلة، والبرامج التعليمية، ووثائق التهيئة، والأسئلة الشائعة بلغة بسيطة.
التوثيق عرض
📦
debugging
79تصحيح مشكلات التعليمات البرمجية بشكل منهجي
تهدر الأخطاء وقت المهندسين عندما تخفي الأعراض السبب الحقيقي. ترشد هذه المهارة إلى إعادة إنتاج المشكلة بشكل منظم، وعزلها، وتحليل السبب الجذري، وإصلاحها، ومنع تكرارها.
البرمجة والتطوير عرض
📦
task-planning
79تخطيط مهام Agile وقوائم Sprint Backlog
غالبا ما تحول الفرق أفكار الميزات العامة إلى عناصر عمل غير واضحة. تنظم هذه المهارة الميزات في قصص مستخدمين، ومعايير قبول، ومهام، وأولويات، وخطط sprint.
الإنتاجية عرض
مهارات ذات صلة
عرض الكل📦
slash-command-encoder
82إنشاء أوامر Slash لسير عمل الذكاء الاصطناعي
بواسطة DNYoussef
تكون سير عمل الذكاء الاصطناعي المتكررة بطيئة عندما يعتمد المستخدمون على مطالبات طويلة باللغة الطبيعية. تساعد هذه المهارة في تعريف أوامر Slash موجزة مع التوجيه، والتحقق، والتسلسل، ونص المساعدة.
الإنتاجية عرض
📦
project-creator
82إنشاء مساحات عمل لمشاريع CCGG
بواسطة DaronVee
غالبًا ما يغفل إعداد المشروع متطلبات العمليات المشتركة والفهرس والتسجيل. ترشد هذه المهارة Claude وCodex وClaude Code خلال إنشاء مشاريع CCGG بشكل منظم باستخدام القوالب وفحوصات التحقق.
الإنتاجية عرض
📦
skills-cli
79إدارة Agent Skills من CLI
بواسطة xixu-me
قد يكون العثور على Agent Skills وصيانتها غير متسق عبر الأدوات والأجهزة. تمنح هذه المهارة الوكلاء سير عمل CLI واضحًا للاكتشاف، والتثبيت، والتحديثات، والإزالة، والنسخ الاحتياطي، والاستعادة.
الإنتاجية عرض
📦
building-agents
85بناء وكلاء Claude Code
بواسطة C0ntr0lledCha0s
يتطلب إنشاء وكلاء AI موثوقين مخططات واضحة وأدوات آمنة وخطوات مراجعة قابلة للتكرار. ترشد هذه المهارة تصميم الوكلاء والتحقق منهم وترحيلهم وصيانتهم ضمن سير عمل Claude Code.
البرمجة والتطوير عرض
📦
agent-development
85بناء وكلاء Claude Code
بواسطة Dami-Randle
تصميم وكلاء Claude Code موثوقين صعب من دون بنية واضحة. توفر هذه المهارة قوالب وقواعد تحقق وأمثلة لمطالبات الوكلاء والمشغلات والأدوات والبيانات الوصفية.
البرمجة والتطوير عرض
📦
building-commands
84إنشاء أوامر Claude Code المائلة
بواسطة C0ntr0lledCha0s
تحتاج الفرق إلى سير عمل AI قابلة للتكرار وسهلة الاستدعاء والمراجعة. تساعد هذه المهارة على إنشاء أوامر Claude Code المائلة وتحديثها والتحقق منها وتوثيقها.
البرمجة والتطوير عرض