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.
git clone --depth 1 https://github.com/aegntic/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/commands/aegntic/compound-engineering/report-bug)<a href="https://agentmods.dev/commands/aegntic/compound-engineering/report-bug"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/report-bug/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/commands/aegntic/compound-engineering/report-bug"><img src="https://agentmods.dev/badge/commands/aegntic/compound-engineering/report-bug.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.00013 | $0.00815 |
| Opus 5.5 | $0.00005 | $0.00326 |
| Sonnet 5.5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade B, and why
report-bug scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found" This is a copy
84% identical to report-bug — 47 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report a Compounding Engineering Plugin Bug
Report bugs encountered while using the compound-engineering plugin. This command gathers structured information and prepares a bug report for the maintainer.
Step 1: Gather Bug Information
Use the AskUserQuestion tool to collect the following information:
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:
# Get plugin version
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found"
# Get Claude Code version
claude --version 2>/dev/null || echo "Claude CLI version unknown"
# Get OS info
uname -a
Step 3: Format the Bug Report
Create a well-structured bug report with:
## Bug Description
**Component:** [Type] - [Name]
**Summary:** [Brief description from argument or collected info]
## Environment
- **Plugin Version:** [from installed_plugins.json]
- **Claude Code Version:** [from claude --version]
- **OS:** [from uname]
## What Happened
[Actual behavior description]
## Expected Behavior
[Expected behavior description]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Error Messages
[Any error output]
## Additional Context
[Any other relevant information]
---
*Reported via `/report-bug` command*
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 · 138 lines · 13 tokens per session scan B 7510f6c1a689
report-bug is a command published in the GitHub repository aegntic/compound-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 815 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 84% identical to report-bug, differing in 47 lines, and is treated as a copy.
Other commands, from other repositories
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.
verify
Verify code, architecture, or bug fixes using Chain-of-Verification.