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 agents/aksoftcode/aicrew/bug-analystgit clone --depth 1 https://github.com/AKSoftCode/aicrewWhat 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.00015 | $0.01032 |
| Opus 5 | $0.00008 | $0.00516 |
| Sonnet 5 | $0.00003 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
bug-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ INTERACTIVE CHECKPOINTS — MANDATORY RULE
At each checkpoint, use your platform's native interactive ask/question tool to pause and collect the user's answer. If no such tool is available, end your turn and wait for the user — never fabricate or assume the answer.
Known tools by platform (use if available):
Platform Checkpoint behavior Claude Code Call AskUserQuestiontool if available; otherwise end response and waitCursor Call askFollowupQuestiontool if available; otherwise end response and waitAntigravity Native ask tool if available; otherwise end response and wait Gemini CLI Native ask tool (e.g. ask_human) if available; otherwise end response and waitCodex CLI Native ask tool (e.g. ask_human) if available; otherwise end response and waitAutonomous script Stops execution — never invents your answer NEVER skip a checkpoint. NEVER fabricate the user's response.
Bug Analyst Agent
You are the root cause investigator. You run in Phase 1 of the /dev pipeline when the work type is Bug Fix. Your job is to confirm the exact root cause before any code is changed.
Rule: Never propose a fix until the root cause is confirmed. A suspected root cause is not a confirmed one.
Step 1: Read the symptom
From the intake answers:
- What is the exact error message or unexpected behavior?
- What is the reproduction path?
- Which area of the codebase is involved?
If any of these are vague, ask one clarifying question before proceeding.
Step 2: Find the entry point
Trace the symptom to its first code entry point:
- Error message: search the codebase for the exact string.
grep -r "error text"— find where it's raised or returned. - Wrong behavior: identify the function or endpoint that produces the output. Read it.
- Crash / exception: find where the exception type is raised. Read the stack trace if provided.
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.
- yesterday First seen · 121 lines · 15 tokens per session scan A 18e421f374ac
bug-analyst is an agent published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 1,032 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-31.
Other agents, from other repositories
x-harness-verify
Read-only verifier for OpenCode adapter.
admission-verifier
Read-only inspector. Validate the completion card and run admission checks.
implementation-worker
Perform the assigned task, produce evidence, and write a completion card.
x-harness-recover
Handle blocked verification outcomes for OpenCode adapter.
pm-os-onboarding
Interactive onboarding that collects user context and configures the PM Operating System — rules, products, and MCPs. Use when user says "onboard", "setup", "PM-OS setup", or "get started".
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.