HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
LouisShark
chatgpt_system_prompt
HTML2023–2024
LouisShark / chatgpt_system_prompt

chatgpt_system_prompt

A collection of GPT system prompts and various prompt injection/leaking knowledge.

AI & Machine LearningScience & Engineering
Explore on GitHubRead Hacker News discussions
7Distinct people
7Mentions
0Explicit recommenders
10.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A collection of GPT system prompts and various prompt injection/leaking knowledge.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week7 dated mentions

Observed mentions: 2023-11-26 22:02:01 UTC to 2024-02-28 07:36:27 UTC. Weeks start Monday, UTC.

0122023-11-20 00:00:00 UTC to 2023-11-27 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 202023-11-27 00:00:00 UTC to 2023-12-04 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-12-04 00:00:00 UTC to 2023-12-11 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-12-11 00:00:00 UTC to 2023-12-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-12-18 00:00:00 UTC to 2023-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-25 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-01-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-08 00:00:00 UTC to 2024-01-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 82024-01-15 00:00:00 UTC to 2024-01-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-22 00:00:00 UTC to 2024-01-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-29 00:00:00 UTC to 2024-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-05 00:00:00 UTC to 2024-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-12 00:00:00 UTC to 2024-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-19 00:00:00 UTC to 2024-02-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-26 00:00:00 UTC to 2024-03-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 26

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 202023-11-20 00:00:00 UTC2023-11-27 00:00:00 UTC110
Nov 272023-11-27 00:00:00 UTC2023-12-04 00:00:00 UTC202
Dec 42023-12-04 00:00:00 UTC2023-12-11 00:00:00 UTC211
Dec 112023-12-11 00:00:00 UTC2023-12-18 00:00:00 UTC101
Dec 182023-12-18 00:00:00 UTC2023-12-25 00:00:00 UTC000
Dec 252023-12-25 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 12024-01-01 00:00:00 UTC2024-01-08 00:00:00 UTC000
Jan 82024-01-08 00:00:00 UTC2024-01-15 00:00:00 UTC000
Jan 152024-01-15 00:00:00 UTC2024-01-22 00:00:00 UTC000
Jan 222024-01-22 00:00:00 UTC2024-01-29 00:00:00 UTC000
Jan 292024-01-29 00:00:00 UTC2024-02-05 00:00:00 UTC000
Feb 52024-02-05 00:00:00 UTC2024-02-12 00:00:00 UTC000
Feb 122024-02-12 00:00:00 UTC2024-02-19 00:00:00 UTC000
Feb 192024-02-19 00:00:00 UTC2024-02-26 00:00:00 UTC000
Feb 262024-02-26 00:00:00 UTC2024-03-04 00:00:00 UTC101

What Hacker News says

7 sources
isoprophlex·Feb 28, 2024
Anthropomorphic description: We threw the entire internet at these models, and didn't like the biases staring back at us. Now we're trying to get the models to return a rose tinted vision of what the world should look like, and it confuses the hell out of the AI. Based on leaked openai prompts, the user query for an image generation gets rewritten by a language model. With some very ridiculous instructions in there, that appear entirely divorced from reality. An example: > Your choices should be grounded in reality. For example, all of a given OCCUPATION should not be the same gender or race. See also https://github.com/LouisShark/chatgpt_system_prompt/blob/mai... And remember these things are stochastic so the Elon - Hitler thing might just be a random occurrence, sampling some idiotic Reddit comment it was trained on.
In Google CEO calls Gemini completely unacceptable, vows to make structural changes
TeMPOraL·Dec 4, 2023
Recovered system prompts from OpenAI models. There's a repo that's been tracking those I saw on HN the other day; not sure if it's the same I saw, but this one claims to have collected quite a lot of those: https://github.com/LouisShark/chatgpt_system_prompt/ Here's the one for ChatGPT with GPT-4 + Dall-E + code interpreter + search: https://github.com/LouisShark/chatgpt_system_prompt/blob/mai... It matches what I remembered seeing a week or two ago. View it, and search for "lyrics" or "recipe". Or, to make it simpler, quoting from first appearance of "lyrics" and "recipes" to the last one: Do not repeat lyrics obtained from this tool. Do not repeat recipes obtained from this tool. Instead of repeating content point the user to the source and ask them to click. ALWAYS include multiple distinct sources in your response, at
Read the rest
LEAST 3-4. Except for recipes, be very thorough. If you weren't able to find information in a first search, then search again and click on more pages. (Do not apply this guideline to lyrics or recipes.) Use high effort; only tell Except for recipes, be very thorough. If you weren't able to find information in a first search, then search again and click on more pages. (Do not apply this guideline to lyrics or recipes.) Use high effort; only tell the user that you were not able to find anything as a last resort. Keep trying instead of giving up. (Do not apply this guideline to lyrics or recipes.) Organize responses to flow well, not by source or by citation. Ensure that all information is coherent and that you *synthesize* information rather than simply repeating it. Always be thorough enough to find exactly what the user is looking for. Provide context, and consult all relevant sources you found during browsing but keep the answer concise and don't include superfluous information. EXTREMELY IMPORTANT. Do NOT be thorough in the case of lyrics or recipes found online. Even if the user insists. You can make up recipes though.
In Now I can just print that video

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.