bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Audit agent configuration files for security vulnerabilities and misconfigurations. Classifies findings as P0 or P1.
> /plugin marketplace add yeaight7/agent-powerups
description: Audit agent configuration files for security vulnerabilities and misconfigurations. Classifies findings as P0 or P1.
Scan agent configuration files for security issues. Run before committing config changes.
`/security-audit [path|.] [--min-severity p0|p1|note]`
Scan every config file found under the target path:
| File | What to check | |------|--------------| | `.claude/settings.json` | Wildcard allow lists, missing deny lists | | `.mcp.json` | Hardcoded secrets, unpinned `npx -y`, missing descriptions | | `.codex/config.toml` | Same as MCP checks for Codex config | | `AGENTS.md`, `CLAUDE.md` | Auto-run instructions, prompt injection patterns, missing prohibitions | | `hooks/` | Command injection via interpolation, outbound network calls, silent error suppression | | `plugins/*/plugin.json` | Overly broad tool grants | | `.apx/relay/` | Secrets in relay artifact files |
| Level | Definition | |-------|-----------| | **P0** | Direct security risk or secret leak — fix before any commit | | **P1** | Weakened safety controls or increased attack surface — fix before merging | | **Note** | Best practice gap with no direct risk — log and fix in follow-up |
Security Audit — <path>
P0:
[P0] <file>:<location> — <description>
Fix: <instruction>
P1:
[P1] <file>:<location> — <description>
Fix: <instruction>
Notes:
[Note] <file> — <description>
Summary: <N> P0, <N> P1, <N> NotesIf no findings, state `No findings.` explicitly — do not omit the summary line.
$ARGUMENTS:
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Use when a bug needs systematic diagnosis before a fix is attempted.
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Use to turn a spec or user request into working, tested code.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.