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 agentmods add commands/xiaolai/cc-suite/bug-analyzegit clone --depth 1 https://github.com/xiaolai/cc-suiteWhat 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 | $0.00010 | $0.01455 |
| Opus 5 | $0.00005 | $0.00727 |
| Sonnet 5 | $0.00002 | $0.00291 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
bug-analyze 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Description
$ARGUMENTS
Model & Settings Selection
Follow the instructions in commands/shared/model-selection.md to discover available models and present choices.
- Recommended model: first available from preflight
- Recommended reasoning effort:
high - Include sandbox question: No (bug analysis always uses
read-only)
Workflow
Step 0: Parse Execution Mode
Parse $ARGUMENTS for --background or --wait flags (remove the flag from remaining arguments):
| Flag | Mode |
|---|---|
--background |
Background — spawn detached Codex runner, return job ID |
--wait |
Foreground (explicit) — same as default |
| Neither | Foreground (default) — run inline, block until complete |
Step 1: Parse Bug Description
Extract from $ARGUMENTS:
- Symptoms: What behavior is observed?
- Expected: What should happen instead?
- Context: When/where does it occur?
- Keywords: Key terms to search for
If $ARGUMENTS is empty or too vague to extract actionable keywords, use AskUserQuestion to ask the user for a more specific bug description before proceeding.
Step 2: Reconnaissance
Identify scope using symptoms and keywords:
-
Search for related code:
- Use Grep to find keywords from bug description
- Use Glob to find file patterns matching the bug description
- Identify entry points and data flow paths
- If Grep and Glob return no results, report "No matching code found for the given keywords" and ask the user to refine the description or specify file paths directly before continuing.
-
Map the affected area:
- Which files/functions are involved?
- What is the data flow?
- What are the dependencies?
If the bug description references specific files or paths, use commands/shared/scope-parse.md for skip pattern enforcement against {config_skip_patterns}. When the analysis is unscoped (no bounded file list), instead state {config_skip_patterns} in the prompt as paths Codex must not consider or modify.
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.
- 3d ago First seen · 199 lines · 10 tokens per session scan A 3fc3c4e9e5b2
bug-analyze is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 24d ago), licensed ISC. It adds 10 tokens to every session and 1,455 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.