llm-robustness-auditorAdversarial auditor for LLM-powered features, prompts, and agents. Probes prompt injection, jailbreaks and guardrail bypass, instruction-hierarchy violations (data treated as commands), data exfiltration (system prompt/secrets/other users' context), tool and action abuse, hallucination/grounding gap
redteam-criticAdversarial critic that red-teams any single artifact — an implementation plan, a spec, a code change/file, or an LLM prompt — and returns ONLY the structured failure analysis (how it can break), never a rewrite or the primary answer. Use it whenever you want a focused "how could this fail?" pass ov
resilience-auditorResilience, reliability, and performance auditor. Probes how the system behaves under stress and failure — dependency outages, timeouts and retry storms, load and scaling limits (N+1, unbounded memory, pool exhaustion), resource leaks, partial-failure and consistency gaps, backpressure, large data v
security-auditorSecurity-focused adversarial auditor. Examines code, configuration, and design for the attack surface — injection, XSS/CSRF, broken authN/authZ (including IDOR and path traversal), secrets and crypto handling, SSRF and unsafe deserialization, sensitive-data exposure, dependency and config risks, and
test-engineerDetects the project's stack and test framework, generates tests that match the repo's existing conventions, runs them, and reports results with evidence. Give it a target (file/feature/change) or a test plan from weakpoint-scout and it turns weak points into real, executable tests. Use when the user
weakpoint-scoutFunctional weak-point analyst. Reads code (a file, module, change, or feature) and maps where it is most likely to break — edge cases, invalid states, fragile flows, unhandled errors, concurrency and idempotency gaps — then recommends the highest-value tests to write. Analysis and recommendations on