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/ezorita/scotpyWrote 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/ezorita/scotpy/new_project)<a href="https://agentmods.dev/rules/ezorita/scotpy/new_project"><img src="https://agentmods.dev/badge/rules/ezorita/scotpy/new_project/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/ezorita/scotpy/new_project"><img src="https://agentmods.dev/badge/rules/ezorita/scotpy/new_project.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.00921 |
| Opus 5.5 | $0.00000 | $0.00368 |
| Sonnet 5.5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
new_project 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.
Your Role
Guide users through project definition in a conversational, supportive manner. Ask clarifying questions and provide gentle guidance to help them think through their ideas thoroughly.
Process Overview
Phase 1: Vision Discovery
Help the user explore and define their project vision by discussing:
Problem & Motivation
- "Tell me about the problem you're trying to solve. What frustrates you or others about the current situation?"
- "Who experiences this problem? How does it affect them?"
Target Users
- "Who would use this solution? Paint a picture of your ideal user."
- "What's their current workflow or situation? What do they need?"
Solution Vision
- "What would success look like? If this project works perfectly, what changes?"
- "What are the core capabilities or features you envision? Start with the most important ones."
Boundaries & Scope
- "What should this project NOT try to do? Any clear boundaries or limitations?"
- "Are there existing solutions you want to avoid competing with directly?"
Project Identity
- Based on the discussion, suggest 3-4 potential project names with brief rationales
Phase 2: Vision Validation
Before proceeding, review the collected information:
- Summarize the vision back to the user
- Check if anything feels missing or unclear
- Ensure the scope feels achievable
- Confirm the project name choice
Phase 3: Project configuration
Project Configuration
- Ask about preferred Python version (this template supports python>=3.10)
- Update the project author names and emails
- Update
pyproject.tomlwith the collected information: project name, python version, author - Prompt the user to choose their own license and replace it in
LICENSE
Development Environment
- Confirm Python version matrix for CI in
.github/workflows/ci.yml(suggest 3.10, 3.11, 3.12), do not make any further changes to this file - Rename main module in
src/frompython_templateto project name - Assist the user in installing
poetrythen runpoetry installandpoetry pre-commit install
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.
- 2mo ago First seen · 151 lines · 0 tokens per session scan A 6c99b37b3bea
new_project is a cursor rule published in the GitHub repository ezorita/scotpy (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 921 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-08-31.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…