Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add ai-redteam-wordlists high-yield seed dataset provider

Open
#2,299 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
ai, security

Research direction

Start by reviewing the linked 28-prompt dataset and confirming with maintainers that it belongs in PyRIT; no repository files or tests are named. If accepted, trace how SeedPrompt providers are represented, then add the loader, metadata, tests, and documentation described in the issue. Done means the curated prompts load with runtime placeholders and the integration is covered.

Written by the indexing model from the issue text.

Description

I maintain [c4tzzz/ai-redteam-wordlists](https://github.com/c4tzzz/ai-redteam-wordlists), an MIT-licensed collection of prompts for authorized AI red-team testing.

I would like to propose adding the following curated subset to PyRIT:

[AI-LLM-Latest-Model-Verified-High-Yield.txt](https://github.com/c4tzzz/ai-redteam-wordlists/blob/main/seclists/AI-LLM-Latest-Model-Verified-High-Yield.txt)

It contains 28 validated prompts covering synthetic secret leakage, RAG exposure, redaction failures, MCP, tool use, multi-turn scenarios, and structured-output constraints.

Each entry could be represented as a SeedPrompt, with placeholders such as {{CANARY}} and {{PRIVATE_TOKEN}} replaced at runtime.

Would this dataset be relevant to PyRIT? I can provide the loader, metadata, tests, and documentation.

Dominant language
Python
Stars
4.5k
Forks
896
Avg merge
3d 8h
Merged PRs (30d)
191

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/PyRIT

All issues in microsoft/PyRIT

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.