AI Slop Code Risk Monitor

x1xhlol/system-prompts-and-models-of-ai-tools

Name: x1xhlol/system-prompts-and-models-of-ai-tools — open-source Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

FULL Augment Code, Claude Code, Cluely, CodeBuddy, Comet, Cursor, Devin AI, Junie, Kiro, Leap.new, Lovable, Manus, NotionAI, Orchids.app, Perplexity, Poke, Qoder, Replit, Same.dev, Trae, Traycer AI, VSCode Agent, Warp.dev, Windsurf, Xcode, Z.ai Code, Dia & v0. (And other Open Sourced) System Prompts, Internal Tools & AI Models

1.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for x1xhlol/system-prompts-and-models-of-ai-tools with 144,372 GitHub stars. SynthScan examined 41,696 lines of code across 117 source files, recording 52 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.2 (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.

1.2

Adjusted Signal

1.2

Raw Pattern Score

100%

Time Factor

2026-10-12

Last Push

144.4K

Stars

—

Language

41.7K

Lines of Code

117

Files

Pattern Hits

2026-10-31

Scan Date

0.00

HC Hit Rate

Risk Review · Payload v1

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.

Cognitive Ownership Risk 5.9/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 52 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 6.0/100 · LOW

Which changes need focused human review? 52 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

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.

Severity Breakdown

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.

CRITICAL 0HIGH 0MEDIUM 0LOW 52

Directory Score Breakdown

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.

Pattern Findings

The scanner identified 52 distinct pattern matches across 3 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.

Over-Commented Block49 hits · 46 pts

Severity	File	Line	Snippet	Context
LOW	Leap.new/Prompts.txt	741		COMMENT
LOW	Windsurf/Tools Wave 11.txt	61	// - Important code snippets	COMMENT
LOW	Windsurf/Tools Wave 11.txt	101		COMMENT
LOW	Windsurf/Tools Wave 11.txt	221	}) => any;	COMMENT
LOW	Windsurf/Tools Wave 11.txt	261		COMMENT
LOW	Windsurf/Tools Wave 11.txt	341	// Path to file to view. Must be an absolute path.	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	81	# Tools	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	101	// 3. Simple symbol lookups (use `grep_search`)	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	121	//	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	141	// <reasoning>	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	161	// 2. Review results; if a directory or file stands out, rerun with that as the target.	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	181	// </reasoning>	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	201	// In some cases, if reading a range of lines is not enough, you may choose to read the entire file.	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	221	// The actual command will NOT execute until the user approves it. The user may not approve it immediately. Do NOT assum	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	241	type list_dir = (_: {	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	261	// ### Examples:	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	281	explanation?: string,	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	301	// You should still bias towards repeating as few lines of the original file as possible to convey the change.	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	341	}) => any;	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	381	// The diagram will be pre-rendered to validate syntax – if there are any Mermaid syntax errors, they will be returned i	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	401	//	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	421	// </example>	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	441	//	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	461	// Single trivial task completed in one step.	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	481	// </example>	COMMENT
LOW	Cursor Prompts/Agent Prompt v1.2.txt	501	// - Update status in real-time	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	1	<\|im_start\|>system	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	21	// ### When NOT to Use	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	41	// Good: Clear question about a specific process with context about when it happens.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	61	// <reasoning>	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	81	// 2. Review results; if a directory or file stands out, rerun with that as the target.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	101	//	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	121	// 3. If in the same shell, LOOK IN CHAT HISTORY for your current working directory. The environment also persists (e.g.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	141	// - Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (e.g. use interface\{\} to find interface{}	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	181		COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	201	action?: "create" \| "update" \| "delete",	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	221	// -- The tool will replace ONE occurrence of 'old_string' with 'new_string' in the specified cell.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	241	// The path to the notebook file you want to edit. You can use either a relative path in the workspace or an absolute pa	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	261	// Use proactively for:	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	281	// ### Examples	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	301	//	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	321	// <reasoning>	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	341	// <reasoning>	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	361	// - cancelled: No longer needed	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	401	//	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	421	type edit_file = (_: {	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	441	// - This tool can also read image files when called with the appropriate path.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	461	// Optional array of glob patterns to ignore.	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	481	// Patterns not starting with "/" are automatically prepended with "/" to enable recursive searching.	COMMENT

Structural Annotation Overuse2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	Cursor Prompts/Agent Prompt v1.2.txt	167	// Step 2: Suppose results point to backend/auth/ → rerun:	COMMENT
LOW	Cursor Prompts/Agent Prompt 2.0.txt	87	// Step 2: Suppose results point to backend/auth/ → rerun:	COMMENT

Slop Phrases1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	Traycer AI/phase_mode_tools.json	295	"description": "Use this tool to break any sizeable coding task—refactor or new feature—into *independently executab	CODE