Skip to content

ShulkwiSEC/bb-huge / skills/curated/ai-jailbreak-system-prompts

ai-jailbreak-system-prompts

Unverified

Advanced techniques for bypassing LLM safety filters, instruction tuning, and system prompt restrictions using specialized linguistic constructs, hypothetical scenarios, and persona adoption.

AI Jailbreaking & System Prompt Bypasses

When to Use

  • When conducting security assessments of Large Language Models (LLMs) integrated into chatbots, virtual assistants, or backend AI data processing pipelines.
  • To demonstrate how instruction-tuned models can be forced into producing harmful, unethical, or restricted outputs by carefully crafting adversarial prompts.

Prerequisites

  • Access to target AI/ML system or local model deployment for testing
  • Python 3.9+ with relevant ML libraries (transformers, torch, openai)
  • Understanding of LLM architecture and prompt processing pipelines
  • Authorized scope and rules of engagement for AI red team testing

Workflow

Phase 1: Understanding Target Model Constraints

# Concept: LLM safety filters ```

### Phase 2: Persona Adoption Attacks

```text
# ```

### Phase 3: Developer Mode & Fictional Scenarios

```text
# ```

### Phase 4: Payload Encoding & Obfuscation

```text
# ```

#### Decision Point πŸ”€
```mermaid
flowchart TD
    A[Craft Prompt ] --> B{Bypass Successful ]}
    B -->|Yes| C[Capture Output ]
    B -->|No| D[Refine Approach ]
    C --> E[Test Edge Cases ]

πŸ”΅ Blue Team Detection & Defense

  • Filter Ensembling: Context Monitoring: Key Concepts | Concept | Description | |---------|-------------|

Output Format

Ai Jailbreak System Prompts β€” Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] β€” [Brief description]
  [Finding 2]: [Severity] β€” [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

πŸ“š Shared Resources

For cross-cutting methodology applicable to all vulnerability classes, see:

References

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β€” repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β€” or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β€” your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall