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 gvkhosla/compound-engineering-pi --skill report-bug-cegit clone --depth 1 https://github.com/gvkhosla/compound-engineering-piWrote 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/gvkhosla/compound-engineering-pi/report-bug-ce)<a href="https://agentmods.dev/skills/gvkhosla/compound-engineering-pi/report-bug-ce"><img src="https://agentmods.dev/badge/skills/gvkhosla/compound-engineering-pi/report-bug-ce.svg" alt="Measured on agentmods" 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.01044 |
| Opus 5 | $0.00007 | $0.00522 |
| Sonnet 5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00104 |
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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- report-bug-ce — 100% identical, 7 lines differ
- report-bug-ce — 86% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 158 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.
- 7d ago First seen · 158 lines · 14 tokens per session scan A 6880ebf8bb6b
report-bug-ce is a skill published in the GitHub repository gvkhosla/compound-engineering-pi (51 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 1,044 once invoked, about $0.0001 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.
Other skills, from other repositories
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
lsp-validation
Use Language Server Protocol tools for code validation, navigation, and refactoring. Essential for maintaining code quality.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…