Skip to main content

​
Contributing to the Collection

This collection thrives on community contributions. Whether you’ve extracted a new system prompt, found an updated version, or want to improve documentation, we welcome your input.
Repository: github.com/asgeirtj/system_prompts_leaksMaintainer: asgeirtj (Discord: asgeirtj)

​
What We Accept

  • Prompts from major AI models (Claude, GPT, Gemini, etc.)
  • Prompts from AI products (ChatGPT, Claude.ai, Gemini, etc.)
  • Tool-specific prompts (Canvas, Code Interpreter, etc.)
  • API vs. web interface variants
  • Different personality/mode variants
  • Updated versions of existing prompts
  • Typo fixes and clarifications
  • Better organization of existing prompts
  • Metadata additions (extraction date, version, etc.)
  • Comparative analysis between prompts
  • Extraction scripts (with ethical usage guidelines)
  • Analysis tools for comparing prompts
  • Visualization of prompt structures
  • Documentation generators

​
Contribution Guidelines

​
Format Requirements

1

File Naming

Use descriptive, lowercase names with hyphens:✅ Good:
  • claude-sonnet-4.6.md
  • gpt-5.1-default.md
  • gemini-2.5-pro-webapp.md
  • tool-canvas-canmore.md
❌ Avoid:
  • prompt.txt
  • ClaudeSystemPrompt.md
  • new-file-1.md
2

Directory Structure

Organize by company:
/Anthropic/
  claude-sonnet-4.6.md
  claude-opus-4.6.md
  /old/
    claude-3.7-sonnet.md
  /raw/
    claude-opus-4.6-no-tools-raw.md

/OpenAI/
  gpt-5.1-default.md
  gpt-5.1-friendly.md
  /API/
    gpt-5.3-chat-api.md
  /Old/
    gpt-4.5.md

/Google/
  gemini-2.5-pro-webapp.md
  gemini-3-pro.md

/Misc/
  [Other AI systems]
Move outdated versions to /old/ subdirectories.
3

File Format

Use Markdown (.md) format:
[Optional: Link to live prompt or context]

[The actual system prompt content]

[Optional: Notes about extraction method, date, or variations]
Preserve original formatting, including XML tags, special delimiters, and whitespace that may be significant.
4

Metadata

Add a comment or header with:
  • Extraction date
  • Model/product version
  • Interface (API, web, mobile, etc.)
  • Any special conditions (free tier, paid, beta, etc.)
Example:
<!-- 
Extracted: 2026-02-17
Model: Claude Sonnet 4.6
Interface: claude.ai web interface
Account: Free tier
-->

​
Pull Request Process

1

Fork the Repository

  1. Go to github.com/asgeirtj/system_prompts_leaks
  2. Click “Fork” in the top right
  3. Clone your fork locally:
git clone https://github.com/YOUR_USERNAME/system_prompts_leaks.git
cd system_prompts_leaks
2

Create a Branch

git checkout -b add-[model-name]-prompt
Example: add-claude-opus-4.7-prompt
3

Add Your Files

  1. Place files in appropriate directories
  2. Follow naming conventions
  3. Include metadata
  4. Move old versions to /old/ if applicable
git add Anthropic/claude-opus-4.7.md
git commit -m "Add Claude Opus 4.7 system prompt from claude.ai"
4

Push and Create PR

git push origin add-[model-name]-prompt
Then:
  1. Go to your fork on GitHub
  2. Click “Compare & pull request”
  3. Fill out the PR template (see below)
  4. Submit!

​
Pull Request Template

## Description
[Brief description of what you're adding]

## Prompt Details
- **Model/Product**: [e.g., Claude Sonnet 4.7]
- **Interface**: [e.g., claude.ai web, API, mobile app]
- **Extraction Date**: [YYYY-MM-DD]
- **Extraction Method**: [Brief description, if notable]

## Changes
- [ ] New system prompt added
- [ ] Updated existing prompt
- [ ] Moved old version to /old/
- [ ] Added metadata
- [ ] Documentation improvements

## Verification
- [ ] I have verified this prompt is accurate
- [ ] I have checked for duplicates
- [ ] I have followed naming conventions
- [ ] I have added appropriate metadata

## Additional Notes
[Any special context, variations, or observations]

​
Ethical Guidelines

Responsible ContributionWhen contributing extracted prompts, please:
  • Respect terms of service and legal boundaries
  • Don’t share personal information or API keys
  • Focus on educational/research value
  • Consider responsible disclosure for security issues

​
What NOT to Include

❌ Don’t contribute:
  • Personal API keys or credentials
  • Prompts from private/enterprise systems without permission
  • Content that violates NDAs or confidentiality agreements
  • Malicious code or exploits (without responsible disclosure first)
  • Personal information about users or conversations

​
Review Process

1

Initial Review

Maintainers will check:
  • Format compliance
  • Naming conventions
  • Duplicate detection
  • Metadata completeness
2

Verification

For new prompts:
  • Attempt to verify accuracy
  • Check extraction date is recent
  • Confirm it’s not a duplicate or minor variant
3

Merge or Feedback

You’ll receive either:
  • ✅ Approval and merge (usually within a few days)
  • 💬 Feedback requesting changes
  • ❌ Rejection with explanation (rare)

​
Documentation Contributions

You can also improve this documentation site!

​
Types of Documentation Improvements

Prompt Analysis

Write analysis comparing prompts, highlighting interesting patterns, or explaining specific techniques

Tutorials

Create guides on prompt engineering, extraction techniques, or using the collection

Comparative Studies

Compare how different companies handle similar challenges

Navigation

Improve organization, tagging, or searchability

​
Documentation Structure

This site uses Mintlify for documentation. Key files:
  • docs/: MDX documentation pages
  • docs.json: Navigation and configuration
  • /resources/: This section you’re reading now
To contribute documentation:
  1. Fork the repository
  2. Edit or create .mdx files in docs/
  3. Update docs.json if adding new pages
  4. Test locally with mintlify dev
  5. Submit a pull request

​
Recognition

Contributors are recognized in:
  • GitHub commit history
  • Repository README (for significant contributions)
  • Release notes for major updates
Star the RepositoryIf you find this collection useful, please ⭐ star the repository on GitHub!Star History Chart

​
Getting Help

1

Check Existing Issues

Search GitHub Issues for similar questions or problems.
2

Discord

Reach out to the maintainer: asgeirtj on Discord
3

Create an Issue

For bugs or feature requests, open a new issue on GitHub.

​
Future Roadmap

We’re always looking to improve the collection. Ideas for future development:
  • Automated extraction monitoring for prompt updates
  • Better diff tools for comparing prompt versions
  • Interactive prompt explorer with search and filtering
  • Analysis dashboard showing prompt evolution over time
  • API for programmatic access to the collection
Want to work on any of these? Reach out or submit a proposal!
Thank you for contributing to the collective understanding of AI system prompts. Your contributions help researchers, developers, and users better understand how AI systems work.

Build docs developers (and LLMs) love

Get started for freeTalk to us