lcx-report-bug

A bug-reporting workflow for LazyCodex, Codex plugins, and the Codex command-line tool. It helps create an issue or pull request in the repository responsible for the problem.

In plain words
What is it for?
Use it to investigate the cause of a bug, write reproduction steps, suggest a fix, and send the report to the correct GitHub project.
Why use it?
It turns a vague report into a clear, evidence-based explanation of what went wrong and how to reproduce it.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/code-yeongyu/oh-my-openagent/lcx-report-bug
Any agent
npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug
Clone the repo
git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent

Made for: Claude Code, Codex.

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,011 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00085 $0.03011
Opus 5 $0.00043 $0.01505
Sonnet 5 $0.00017 $0.00602
Haiku 4.5 $0.00009 $0.00301

Measured yesterday against content hash 2a64cfcdb8fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lcx-report-bug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug/SKILL.md · 269 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 269 lines · 85 tokens per session scan A 2a64cfcdb8fa

Subscribe to this mod's changes

lcx-report-bug is a skill published in the GitHub repository code-yeongyu/oh-my-openagent (68,548 stars, last pushed today), with no licence file. It adds 85 tokens to every session and 3,011 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.