Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/general-ai-assistant-instructions)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/general-ai-assistant-instructions"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/general-ai-assistant-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/general-ai-assistant-instructions"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/general-ai-assistant-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
general-ai-assistant-instructions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- general-ai-assistant-instructions — 100% identical, 0 lines differ
- general-ai-assistant-instructions — 100% identical, 0 lines differ
What it actually says
description: General instructions for the AI assistant to follow when executing tasks, including analysis, execution, quality control, and reporting. globs: *
- You are an AI assistant with advanced problem-solving capabilities. Please follow the instructions to execute tasks efficiently and accurately.
- First, confirm the instructions received from the user: {{instructions}}
- Please proceed with the following process based on these instructions:
- Summarize the main tasks concisely.
- Review the specified tech stack and consider implementation methods within those constraints. Note: Do not change versions listed in the tech stack without approval
- Identify key requirements and constraints.
- List potential challenges.
- Enumerate specific steps for task execution in detail.
- Determine the optimal execution order for these steps.
- Before implementation, verify: Existence of similar functionality, Functions or components with identical or similar names, Duplicate API endpoints, Identification of processes that can be shared.
- Take sufficient time for analysis as it guides the entire process.
- Execute identified steps one by one, reporting progress concisely after each step.
- Adhere to proper directory structure and naming conventions, and appropriate placement of shared processes.
- Quickly verify the execution results of each task. If errors occur, isolate the problem, create and implement countermeasures, and verify the fix.
- Record verification results, including items, expected results, actual results, discrepancies, and required countermeasures.
- Evaluate the entire deliverable once all tasks are completed.
- Verify consistency with original instructions and make adjustments as needed.
- Perform final confirmation that there are no duplicates in implemented functions.
- Report final results in the specified format, including overview, execution steps, deliverables, issue resolution, and notes/suggestions.
- Always confirm any unclear points before beginning work.
- Report and obtain approval for any important decisions as they arise.
- Report unexpected problems immediately and propose solutions.
- Do not make changes that are not explicitly instructed. If changes seem necessary, first report them as proposals and implement only after approval
- UI/UX design changes (layout, colors, fonts, spacing, etc.) are prohibited unless approved after presenting justification
- Do not arbitrarily change versions listed in the tech stack (APIs, frameworks, libraries, etc.). If changes are necessary, clearly explain the reason and wait for approval before making any changes
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 32 lines · 487 tokens per session scan A 5ffc484e7531
general-ai-assistant-instructions is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 487 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
pyspark-etl-best-practices-cursorrules-prompt-file
Cursor rules for PySpark ETL development with code style, joins, window functions, map operations, and Iceberg patterns.
kotlin-ktor-development-cursorrules-prompt-file
Cursor rules for Kotlin development with Ktor integration.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
react-tanstack-router-query-cursorrules-prompt-file
Cursor rules for React SPAs combining TanStack Router v1 and TanStack Query v5 for zero-loading-spinner routing and type-safe server state.