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/supertokens/create-supertokens-appWrote 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/supertokens/create-supertokens-app/python)<a href="https://agentmods.dev/rules/supertokens/create-supertokens-app/python"><img src="https://agentmods.dev/badge/rules/supertokens/create-supertokens-app/python/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/supertokens/create-supertokens-app/python"><img src="https://agentmods.dev/badge/rules/supertokens/create-supertokens-app/python.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.02899 |
| Opus 5.5 | $0.00000 | $0.01160 |
| Sonnet 5.5 | $0.00000 | $0.00580 |
| Haiku 4.5 | $0.00000 | $0.00290 |
Grade A, and why
python 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 1mo 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python
| factor | py imports | py inits |
|---|---|---|
emailpassword |
from supertokens_python.recipe import emailpassword | emailpassword.init() |
thirdparty |
from supertokens_python.recipe import thirdparty | thirdparty.init( sign_in_and_up_feature=thirdparty.SignInAndUpFeature(providers=[ // per-provider config ]) ), |
link_email |
from supertokens_python.recipe import paswordlessfrom supertokens_python.recipe.passwordless import ContactEmailConfig | passwordless.init( flow_type="MAGIC_LINK", contact_config=ContactEmailConfig(), ), |
link_phone |
from supertokens_python.recipe import paswordlessfrom supertokens_python.recipe.passwordless import ContactPhoneConfig | passwordless.init( flow_type="MAGIC_LINK", contact_config=ContactPhoneConfig(), ), |
otp_phone |
from supertokens_python.recipe import paswordlessfrom supertokens_python.recipe.passwordless import ContactPhoneConfig | passwordless.init( flow_type="USER_INPUT_CODE", contact_config=ContactPhoneConfig(), ), |
otp_email |
from supertokens_python.recipe import paswordlessfrom supertokens_python.recipe.passwordless import ContactEmailConfig | passwordless.init( flow_type="USER_INPUT_CODE", contact_config=ContactEmailConfig(), ), |
totp |
from supertokens_python.recipe import totp | totp.init(), |
Notes:
- session, dashboard, userroles also imported for all factors, in addition to their own config.
- if both link_email and link_phone are present as factors, the contact_config in init becomes ContactEmailOrPhoneConfig().
- if both otp_email and otp_phone are present as factors, the flowType in init becomes "USER_INPUT_CODE_AND_MAGIC_LINK".
- If a second factor is present, always include the multifactorauth recipe.
- For any multifactor recipes, also include accountlinking and emailverfiation.
- Second factors specific behavior always go in the override function of the MultiFactorAuth recipe!
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.
- 1mo ago First seen · 325 lines · 0 tokens per session scan A 35909dac472a
python is a cursor rule published in the GitHub repository supertokens/create-supertokens-app (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,899 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-01.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
py-fast-api
Cursor rules for Python FastAPI backend development and best practices.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
aiohttp
This guide defines definitive best practices for using aiohttp, focusing on efficient, robust, and maintainable asynchronous HTTP client code.