A command that runs automated tests and build checks before performing a focused review of the code. For every bug found, it proposes or records a regression test, which is a test that prevents the same problem from returning.

Use it to check a file or project for test failures, build or type errors, and issues that automated checks may miss. It reviews areas such as error cleanup, response consistency, complete queries, and rollback after failed updates.

It ensures basic tests and builds pass before spending time on review. It also stops when those checks fail and records how each discovered bug should be tested.

bug-check — Command for Claude Code by yeaight7/agent-powerups

Install

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.

Clone the repo

git clone --depth 1 https://github.com/yeaight7/agent-powerups

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/yeaight7/agent-powerups/bug-check/github.svg)](https://agentmods.dev/commands/yeaight7/agent-powerups/bug-check)

Your own site

<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/bug-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/bug-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/bug-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/bug-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 355 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00025	$0.00355
Opus 5.5	$0.00010	$0.00142
Sonnet 5.5	$0.00005	$0.00071
Haiku 4.5	$0.00003	$0.00036

Measured 1mo ago against content hash ee49f05c8041, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bug-check 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.

commands/bug-check.md · 56 lines

What it actually says

/bug-check — Automated Bug Check

Mandatory automated checks precede agent review. Do not skip or reorder steps.

Usage

/bug-check [path|.]

Step 1 — Automated Tests (mandatory, cannot skip)

npm test        # or: pytest, cargo test, go test ./...
npm run build   # TypeScript build / type check

Tests fail → report as highest priority; stop here until fixed
Build fails → report type errors as highest priority; stop here until fixed
Both pass → continue to Step 2

Step 2 — Focused Code Review

Review for patterns that automated tests do not catch:

Execution path parity — do all code paths (sandbox, production, feature-flag variants) return the same response shape?
Query completeness — are all fields used in the response present in the query?
Error state cleanup — is stale state cleared when an error is returned?
Optimistic update rollback — is UI state reverted when an API call fails?

Step 3 — Regression Tests

For every bug found and fixed, record one of:

Bug: <description>
File: <path>
Regression test: <test name and assertion>

or if a test cannot be written now:

Bug: <description>
Regression test: DEFERRED — <reason>

Do not silently skip. An explicit deferral is required.

Arguments

$ARGUMENTS:

[path|.] — optional target path

Changes

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 · 56 lines · 25 tokens per session scan A ee49f05c8041

Subscribe to this mod's changes

bug-check is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 20d ago), licensed Apache-2.0. It adds 25 tokens to every session and 355 once invoked, about $0.0001 per session on Opus 5.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.

Code review Testing agent agent-skill agent-skills agents gemini-cli-extension plugin

orch-refine-code

Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.

DekaPrayoga/AurixAgent · 36 tokens

pre-merge-check

Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de merger une branche, pour garantir la qualité et éviter les régressions.

TheBeardedBearSAS/claude-craft · 6 tokens

run-workflow

Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.

Lykhoyda/rn-dev-agent · 49 tokens

bug-check