LEAKED SYSTEM PROMPTS FOR CHATGPT, CLAUDE, GEMINI, GROK, PERPLEXITY, CURSOR, LOVABLE, REPLIT, AND MORE! - AI SYSTEMS TRANSPARENCY FOR ALL! 👐
This report summarizes scanner evidence for elder-plinius/CL4R1T4S with 51,657 GitHub stars. SynthScan examined 50,478 lines of code across 71 source files, recording 30 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.8 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 24 finding(s).
Are imports declared and package/API names verified? 6 finding(s).
Are wrappers, guards, and repeated structures necessary? 3 finding(s).
Which changes need focused human review? 30 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 30 distinct pattern matches across 6 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | SAMEDEV/Same_Dev.txt | 121 | // Read the contents of files. The output of this tool call will be the 1-indexed file contents from start_line_one_inde | COMMENT |
| LOW | SAMEDEV/Same_Dev.txt | 141 | end_line_one_indexed_inclusive?: number, // default: 250 | COMMENT |
| LOW | SAMEDEV/Same_Dev.txt | 161 | relative_file_path: string, | COMMENT |
| LOW | SAMEDEV/Same_Dev.txt | 181 | // WARNING: If you do not follow these requirements: | COMMENT |
| LOW | SAMEDEV/Same_Dev.txt | 221 | // Update the project to the latest version before calling this tool. Deploys the project to Netlify. This tool will ret | COMMENT |
| LOW | SAMEDEV/Same_Dev.txt | 241 | // - List, create, describe, and delete Neon projects | COMMENT |
| LOW | DIA/Dia_DraftSkill.txt | 81 | // Use it as much as possible. Flag every possible bad scrape. Its better to be noisy, than miss logging scenarios | COMMENT |
| LOW | OPENAI/Atlas_10-21-25.txt | 281 | // The `image_gen` tool enables image generation from descriptions and editing of existing images based on specific inst | COMMENT |
| LOW | OPENAI/Atlas_10-21-25.txt | 361 | pinned: boolean, | COMMENT |
| LOW | OPENAI/GPT-4.5_02-27-25.md | 81 | // 2. DO NOT ask for permission to generate the image, just do it! | COMMENT |
| LOW | OPENAI/Codex_Sep-15-2025.md | 121 | // Open a new interactive exec session in a container. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1507 | ### Step 1: Understanding the Skill with Concrete Examples | COMMENT |
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1525 | ### Step 2: Planning the Reusable Skill Contents | COMMENT |
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1549 | ### Step 3: Initializing the Skill | COMMENT |
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1591 | ### Step 4: Edit the Skill | COMMENT |
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1625 | ### Step 5: Validate the Skill | COMMENT |
| LOW | OPENAI/Codex_Desktop/5.6-Sol_SystemPrompt.md | 1635 | ### Step 6: Iterate | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | OPENAI/Codex_Desktop/5.6-Sol_Tools.json | 3240 | "description": "Tools provided by the Codex app.\n\nCreate a separate Codex thread only when the user explicitly ask | CODE |
| MEDIUM | OPENAI/Codex_Desktop/5.6-Sol_Tools.json | 3248 | "description": "Tools provided by the Codex app.\n\nSend a follow-up prompt to an existing Codex thread in the backg | CODE |
| MEDIUM | OPENAI/Codex_Desktop/GPT-6-Astra_Prompts.md | 1746 | ## Experimental multi-agent instructions | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | DIA/Dia_CodingSkill.txt | 48 | - Citations are NEVER followed by punctuation; they are always AFTER periods (e.g. lorem ipsum. [{DIA-SOURCE}](reactjs.o | CODE |
| LOW | DIA/Dia_DraftSkill.txt | 52 | ▫ (e.g. lorem ipsum. ”) | CODE |
| LOW | ANTHROPIC/Claude_Sonnet_3.7_New.txt | 128 | Images from the web are not allowed, but you can use placeholder images by specifying the width and height like | CODE |
| LOW | ANTHROPIC/Claude_Sonnet_3.7_New.txt | 157 | Images from the web are not allowed, but you can use placeholder images by specifying the width and height like | CODE |
| LOW | OPENAI/ChatKit_Docs__Oct-6-25.txt | 347 | { id: "user_123", title: "Jane Doe" }, | CODE |
| LOW | OPENAI/ChatKit_Docs__Oct-6-25.txt | 462 | title: "Jane Doe", | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | ZAI/ZCode/Skills.md | 1433 | - [ ] **No process artifacts in output**: NEVER include version numbers ("V3"), iteration markers, draft labels ("DRAFT" | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | OPENAI/ChatKit_Docs__Oct-6-25.txt | 806 | async def attachment_to_message_content( | CODE |
| LOW | OPENAI/ChatKit_Docs__Oct-6-25.txt | 916 | async def attachment_to_message_content( | CODE |
| LOW | OPENAI/ChatKit_Docs__Oct-6-25.txt | 1047 | async def maybe_update_thread_title( | CODE |