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.
npx skills add Jerrylalala/compound-engineering --skill report-bug-cegit clone --depth 1 https://github.com/Jerrylalala/compound-engineeringWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jerrylalala/compound-engineering/report-bug-ce)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/report-bug-ce"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/report-bug-ce/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/report-bug-ce"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/report-bug-ce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.01054 |
| Opus 5.5 | $0.00006 | $0.00422 |
| Sonnet 5.5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
report-bug-ce 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 1mo ago.
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.
This is a copy
100% identical to report-bug-ce — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report a Compound Engineering Plugin Bug
Report bugs encountered while using the compound-engineering plugin. This skill gathers structured information and creates a GitHub issue for the maintainer.
Step 1: Gather Bug Information
Ask the user the following questions (using the platform's blocking question tool — e.g., AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini — or present numbered options and wait for a reply):
Question 1: Bug Category
- What type of issue are you experiencing?
- Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other
Question 2: Specific Component
- Which specific component is affected?
- Ask for the name of the agent, command, skill, or MCP server
Question 3: What Happened (Actual Behavior)
- Ask: "What happened when you used this component?"
- Get a clear description of the actual behavior
Question 4: What Should Have Happened (Expected Behavior)
- Ask: "What did you expect to happen instead?"
- Get a clear description of expected behavior
Question 5: Steps to Reproduce
- Ask: "What steps did you take before the bug occurred?"
- Get reproduction steps
Question 6: Error Messages
- Ask: "Did you see any error messages? If so, please share them."
- Capture any error output
Step 2: Collect Environment Information
Automatically gather environment details. Detect the coding agent platform and collect what is available:
OS info (all platforms):
uname -a
Plugin version: Read the plugin manifest or installed plugin metadata. Common locations:
- Claude Code:
~/.claude/plugins/installed_plugins.json - Codex:
.codex/plugins/or project config - Other platforms: check the platform's plugin registry
Agent CLI version: Run the platform's version command:
- Claude Code:
claude --version - Codex:
codex --version - Other platforms: use the appropriate CLI version flag
If any of these fail, note "unknown" and continue — do not block the report.
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.
- 1mo ago First seen · 159 lines · 14 tokens per session scan A ab46619cc084
report-bug-ce is a skill published in the GitHub repository Jerrylalala/compound-engineering (6 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 1,054 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to report-bug-ce, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.