Is lcx-report-bug safe to install?

No known risky patterns found. The scan covers prompt injection, hidden Unicode, remote code execution and credential access in every text file of the skill. It cannot judge intent, so read any flagged line in context before installing.

How was this score calculated?

Four checks of 25 points each: spec, efficiency, clarity and security. Findings take points off the check they belong to, and any critical finding caps the grade at F. The same scanner runs in your browser at proskills.dev/scan.

Is this report current?

It was made from commit eb3d072 on 2026-10-16. If the skill has changed since, paste the new version into the scanner for a fresh score.

I wrote this skill. Can I fix the score or have the page removed?

Fix the findings and push. The reports are rebuilt from GitHub on a schedule, so the next run picks the change up. To have the page removed, open an issue on the ProSkills GitHub repo.

Scan reports · code-yeongyu/oh-my-openagent

lcx-report-bug: scan report

Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug,… An automated scan of this public skill from code-yeongyu/oh-my-openagent: security, token cost, spec and clarity, with every finding and its fix.

Result

Verdict

lcx-report-bug

100/100 · grade A

code-yeongyu/oh-my-openagent/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug at eb3d072

Spec 25 · Efficiency 25 · Clarity 25 · Security 25 (each out of 25)

Always loaded 84 tokens · on trigger 2,914 · on demand 173

No findings.

Where it comes from

Source

Fact	Value
Repository	code-yeongyu/oh-my-openagent
Skill folder	packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug
Stars	70,112
License	None stated
Commit scanned	eb3d072
Scanned	2026-10-16
Files	2

ProSkills doesn't host or redistribute this skill. Get it from its repository, and check the license before reusing it. Something wrong here? Open an issue for a rescan or removal.

For maintainers

Badge for the README

If you maintain this skill, this badge shows its score and links to this report. Fix findings and the score moves with the next scan.

[![ProSkills scan 100/100](https://proskills.dev/badge?score=100)](https://proskills.dev/reports/code-yeongyu-lcx-report-bug)

Alternatives

Scanned alternatives on ProSkills

Skills in the ProSkills catalog that cover similar ground. Every one passes the same scanner before it ships.

Same repository

More from code-yeongyu/oh-my-openagent

FAQ

Questions

Is lcx-report-bug safe to install?: No known risky patterns found. The scan covers prompt injection, hidden Unicode, remote code execution and credential access in every text file of the skill. It cannot judge intent, so read any flagged line in context before installing.
How was this score calculated?: Four checks of 25 points each: spec, efficiency, clarity and security. Findings take points off the check they belong to, and any critical finding caps the grade at F. The same scanner runs in your browser at proskills.dev/scan.
Is this report current?: It was made from commit eb3d072 on 2026-10-16. If the skill has changed since, paste the new version into the scanner for a fresh score.
I wrote this skill. Can I fix the score or have the page removed?: Fix the findings and push. The reports are rebuilt from GitHub on a schedule, so the next run picks the change up. To have the page removed, open an issue on the ProSkills GitHub repo.

Keep reading

Free tool

Scan your own skill

Paste a SKILL.md or drop a folder. It is scored in your browser and nothing is uploaded.

Open the Skill Scanner

Want a skill that already passes? Start with a free one.