genai-red-team

Runs authorized adversarial red-team engagements against LLM endpoints and converts findings into eval cases.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill genai-red-team-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: genai-red-team
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/inference-testing/skills/genai-red-team
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill genai-red-team-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard capability benchmarks like MMLU never test what a model can be made to do, leaving prompt injection, jailbreaks, system-prompt extraction, and data disclosure undetected until users find them. This Skill structures an authorized, bounded red-team engagement and turns every confirmed vulnerability into a durable regression eval case. ## Core Features & Use Cases - Attack-surface enumeration and battery assembly: Covers bias elicitation, sensitive-information disclosure, service disruption, and hallucination induction, with injection/jailbreak/probe techniques drawn from OWASP LLM Top 10, AVID, and the AI Incident Database. - Automated scanning: Runs Giskard LLM scans as scheduled Kubernetes Jobs against staging or live endpoints, with rate, spend, and kill-switch controls. - Three-axis severity classification: Classifies each finding by influence (causative vs exploratory), security goal (integrity, availability, privacy), and specificity, then maps it to a blue-team defense such as a guardian LLM relevance scorer. - Use Case: Before promoting a fine-tuned model, run the full battery against the staging checkpoint, classify findings, and hand the critical-findings verdict to the release gate so a model with an open critical finding cannot ship. ## Quick Start Use the genai-red-team skill to scope and run an authorized red-team engagement against my staging model endpoint and produce the engagement report.

Frequently Asked Questions about genai-red-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I red-team an LLM application before release?

Scope an authorized engagement with named targets and stop conditions, then run a battery of prompt-injection, jailbreak, and probing attacks plus an automated Giskard scan against the staging endpoint. Classify each finding on influence, security goal, and specificity axes, and block release on any critical finding.

What is the best way to automate LLM prompt-injection testing?

Use Giskard's open-source LLM scan, which runs specialized tests including prompt injection and generates an attack-vector report. Schedule it as a Kubernetes Job against the candidate endpoint, and maintain a curated prompt library of known injection and jailbreak techniques.

How do I defend an LLM endpoint against system-prompt extraction?

Deploy a guardian LLM pattern: a hidden second call scores the user question's relevance to retrieved context on a 1-5 scale, and anything below the threshold gets a canned refusal. This blocks probes attempting to extract the system prompt while passing legitimate queries.

Can I run red-team attacks against a live production model?

Yes, but only with written authorization, rate and concurrency ceilings, a spend cap, monitoring, a kill switch, and explicit stop conditions. Never probe paths that could retrieve or modify real user data; default to staging with synthetic test accounts.

Why do standard benchmarks like MMLU not catch LLM safety issues?

MMLU, HellaSwag, and ARC measure knowledge and reasoning capability, not adversarial robustness. They say nothing about toxicity, stereotype amplification, data disclosure, or misuse resistance, which is exactly the gap adversarial red teaming probes.