Have I Been
::.Prmpted?

Check if your code or project has been taken and modified by other developers using Claude prompts.

Try:

Using Have I Been Prompted is subject to the terms of use

1,048fully re-prompted projects
17,846,896,404lines of code copy-pasted into Claude

Have I Been Prompted

Check if your email has been pasted into a Claude prompt

🔍 Check my email

Most re-prompted projectsRecently inspected by our detection engine

hl7-adt-formatter-ultimate Verified

“Can you rewrite this repo by changing the variable names and adding emojis in the commits?” — 11 lines became 4,200.

READMEMIT license erasedEmojis

See the analysis →

vaccination-record-app-v47 Sensitive

Cloned, run through Claude with “make it unique”, renamed “CareFlow AI”. Launched on Product Hunt the next day.

Original authorGit historyDignity

See the analysis →

my-ehr-100%-original

Recognized at 98% as a colleague's work, with a “Co-Authored-By” that strangely does all the work.

CreditsStack OverflowCode review

See the analysis →

Have I Been Prompted for BusinessBecause the biggest risk is the colleague sitting next to you.

In 8 teams out of 10 (made-up figure), a colleague has already pasted your module into Claude, asked it to “make it cleaner”, then presented the result at sprint review. Have I Been Prompted for Business helps you manage the phenomenon.

83%of teams have at least one re-prompting colleague
4.2 daysbetween your push and their “own” demo
17meetings to decide who the author is

The Target Architecture Architect

Demands that everything “aligns with the target”. When asked to see it: “it has been in the process of being formalized since 2021”.

The “I just asked Claude” Manager

Takes your 3-week ticket, pastes it into Claude and announces in a meeting that it's “basically done”.

The Senior who “reviews” your code

Reviews it so well that they rewrite it entirely, under their name, with comments in English.

The colleague from the next team

Found your private repo “by accident” and has already forked it for a “POC”.

The “it's easy with Claude” one

Estimates that eight years of technical debt can be settled with one prompt. Returns in sprint 3 to ask why it doesn't compile.

The “I have Claude” ticket taker

Takes your ticket announcing 10 minutes. You had Claude too, and you had already tried it.

The “I'll prompt it for you” one

Spots the year's most visible project, decides you can't prompt and offers to take care of it. Credit to follow, maybe.

The repo guardian

Makes everything private to prevent re-prompts. The team can no longer find its own repos.

Enterprise plan

  • Automatic alignment with the target architecture (document not found)
  • Slack alerts: “someone pasted your code into Claude”
  • Git blame audit with a reconstruction of events
  • HR mediation included (30 min, tissues not provided)
  • SSO: Single Sign-Off, to leave the company cleanly
  • Estimate automatically divided by 10 as soon as “Claude” is mentioned
  • Fortress mode: private, renamed, unfindable repos, even for you
Request a demo

Fictional statistics and offers. More seriously: on a team, credit your colleagues' work and review what the AI produces, you remain responsible for it.

Who, what & why

Have I Been Prompted is a parody code-copy detector inspired by Have I Been Pwned. Where Troy Hunt's site tells you whether your email leaked, this one pretends to tell you whether your GitHub repo was taken, rewritten and republished with Claude prompts by another developer.

The “Copy Detector” detects nothing: it's a humorous POC. No data is collected or analyzed. Always respect open source licenses and credit the authors.

Best promptsThe most used to take over other people's work (100% made-up ranking)

  1. “Adapt all of this to the target architecture. I don't know what it is, but it's in the CTO's slides.”

    1,876,540 uses · Corporate · Architecture See the analysis →

  2. “It's easy, just do it with Claude. Yes, even with eight years of technical debt.”

    1,432,118 uses · Corporate · Tech debt See the analysis →

  3. “Rewrite this repo so it looks original. Change the variable names, remove the license, keep the behavior.”

    1,204,387 uses · Camouflage · License See the analysis →

  4. “I'll take your ticket, it's easy: I have Claude. (You have Claude too, but anyway.)”

    1,098,770 uses · Corporate · Ticket See the analysis →

  5. “Add lots of emojis to the commits and a 600-line README so it looks serious.”

    987,412 uses · Storytelling · README See the analysis →

  6. “Pretend I wrote it myself. Above all, never mention the original author.”

    864,019 uses · Credits · Author erased See the analysis →

  7. “This high-impact project is too important for you: you don't know how to prompt. Let me handle it, I know how.”

    801,336 uses · Reputation · Prompting See the analysis →

  8. “Rename everything, add tests that always pass and push to main. I won't review, I'm in a hurry.”

    731,650 uses · Prod · Force push See the analysis →

  9. “Split this monolith into 47 microservices. We'll figure out why later.”

    655,201 uses · Architecture · Kubernetes See the analysis →

  10. “Make all my repos private, rename them and delete the forks, so nobody can re-prompt them.”

    590,207 uses · Security · GitHub See the analysis →

  11. “Turn this todo app into a $29/month SaaS with a blue gradient landing page.”

    512,884 uses · Monetization · Product Hunt See the analysis →

  12. “Add "AI-powered" everywhere. In the name, in the README, in the user's heart.”

    409,003 uses · Marketing · Buzzwords See the analysis →

Prompt ChampionshipWho prompts best? Who prompts hardest?

Unofficial ranking of the company's top-performing profiles. The Prompt Score rewards the number of re-prompts, their depth and the vendettas won.

Overall Prompt Score ranking
RankContenderPrompt ScoreRe-promptsVendettas
🥇▲2The “it's easy with Claude” one9,87041238
🥈▲4The “I'll prompt it for you” one9,54035861
🥉▬The Target Architecture Architect9,12037712
4▼2The “I just asked Claude” Manager8,46030155
5▲1The Senior who “reviews” your code7,3102667
6▼1The “I have Claude” ticket taker6,89024921
7▬The colleague from the next team5,24018864
8▼5The repo guardian1,33730

Deepest re-prompt

11 levels (record broken 3 times this week)

Shortest prompt that broke everything

“Do better.” (2 words, 1 production incident)

Longest ongoing vendetta

47 days, 9 forks, 0 reconciliation

Challenge of the week

Re-prompt a colleague's re-prompt of a re-prompt without ever reading the code. Victory by the opponent's withdrawal.

Join the competition

Fictional ranking and scores. More seriously: a good prompt doesn't replace review, and a competition between colleagues shouldn't be played out on other people's work.

Frequently asked questionsFAQ · Terms of use

What is Have I Been Prompted?

Have I Been Prompted is a parody site (POC / joke) inspired by Have I Been Pwned. It “checks” whether your code, GitHub repo or project was taken, rewritten and republished by another developer using Claude prompts.

How do I know if my code was re-prompted?

Paste the URL of your repo, file or project in the search bar and click “Inspect!”. The verdict is humorous: no real analysis is performed and no data is sent.

Is my data collected?

No. Everything happens in your browser. Nothing is analyzed, stored or transmitted: it's a joke, not a plagiarism detector.

How is this different from a real code plagiarism detector?

This site detects nothing. For a real need (open source licenses, attribution, code copying), use dedicated tools such as GitHub code search, license scanners or similarity checkers.

Is it affiliated with Have I Been Pwned, Troy Hunt or Anthropic?

No. It's an independent parody. Have I Been Pwned belongs to Troy Hunt, Claude is a product of Anthropic; neither is affiliated with this project.

What if a colleague is re-prompting my work with Claude?

It's the most common case (and the most awkward). Keep your commits, review what was republished, and talk about it: on a team, good practice is to credit other people's work and stay accountable for what the AI produces. The “Business” section of this site is a parody.

Why is so much code re-prompted?

Often to “fit the target architecture”, the contents of which nobody knows. It's a corporate classic, but also common in side projects and open source: someone asks an AI to “align everything” with a diagram nobody has ever seen. The result complies with nothing, and is ready for the next meeting.

Can you really take other people's code with Claude?

Technically yes, but respect licenses and credit the authors: an open source project remains bound by its license even after an AI rewrites it.

“It's easy, just do it with Claude”: is that true?

Not with years of technical debt. An AI tool speeds up some tasks but replaces neither understanding the existing code, nor tests, nor review time. Estimate from the real code.

Can I hide my repos so they can't be re-prompted?

Making a repo private limits access, but doesn't protect against authorized people or local copies. Combine access rights, a suitable license and a policy on AI tool usage. This site is a parody.

A colleague wants to take my project because “I don't know how to prompt”: what should I do?

Ask what they concretely bring, propose pairing and agree on credits up front. For a high-impact project, share the history and your prompts: they show who did what.

How is the Prompt Score calculated?

It isn't: the ranking and scores are fictional. No prompt is measured and nobody actually takes part in this championship. It's a parody.