Loading the registry…
Run OpenAI Codex (the `codex` CLI, GPT models) as a managed subagent from Claude Code — start work in the background and get a run handle back immediately, watch its live event log at a controlled level of detail, interrupt and redirect a run, resume any earlier Codex thread including ones started in the Codex TUI, and collect results as text or schema-validated JSON. Use whenever work is being handed to Codex or GPT, when a second independent model should look at something, when an external agent should keep working while Claude does something else, or when an earlier Codex session needs continuing. Also covers Codex CLI setup, auth, sandbox and config diagnosis. Triggers include: codex, 코덱스, 코덱스로, 코덱스한테, 코덱스에게, GPT, GPT한테, GPT에게 시켜, delegate to codex, run with codex, ask GPT, resume codex. Not for Claude's own subagents, the Task tool, or background Bash — those are Claude doing the work itself. Not for Codex Cloud or `codex mcp-server` / `app-server`.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
8 critical findings reported by cisco-skill-scanner, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'tjdwls101010/codex-in-claude (codex)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'tjdwls101010/codex-in-claude (codex)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
40 findings · 11.8s
v0.3.74
3 findings · 8.1s
v0.1.0
0 findings · 4.1s
v0.1.0
3 findings · 4.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 46 findings above stand exactly as their scanners reported them, at full severity.