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.
npx agentmods add rules/supertokens/create-supertokens-app/typescriptgit 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/typescript)<a href="https://agentmods.dev/rules/supertokens/create-supertokens-app/typescript"><img src="https://agentmods.dev/badge/rules/supertokens/create-supertokens-app/typescript.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02967 |
| Opus 5 | $0.00000 | $0.01484 |
| Sonnet 5 | $0.00000 | $0.00593 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade A, and why
typescript 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 2d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript
| factor | ts imports | ts inits |
|---|---|---|
emailpassword |
import EmailPassword from "supertokens-node/recipe/emailpassword"; | EmailPassword.init() |
thirdparty |
import ThirdParty from "supertokens-node/recipe/thirdparty"; | ThirdParty.init({ signInAndUpFeature: { providers: [ // per-provider config ], }, }), |
link_email |
import Passwordless from "supertokens-node/recipe/passwordless"; | Passwordless.init({ contactMethod: "EMAIL", flowType: MAGIC_LINK", }), |
link_phone |
import Passwordless from "supertokens-node/recipe/passwordless"; | Passwordless.init({ contactMethod: "PHONE", flowType: "MAGIC_LINK", }), |
otp_phone |
import Passwordless from "supertokens-node/recipe/passwordless"; | Passwordless.init({ contactMethod: "PHONE", flowType: "USER_INPUT_CODE", }), |
otp_email |
import Passwordless from "supertokens-node/recipe/passwordless"; | Passwordless.init({ contactMethod: "EMAIL", flowType: "USER_INPUT_CODE", }), |
totp |
import totp from "supertokens-node/recipe/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 contactMethod in init becomes "EMAIL_OR_PASSWORD".
- 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 EmailVerification.
- 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.
- 2d ago First seen · 324 lines · 0 tokens per session scan A 69ce414c855e
typescript is a cursor rule published in the GitHub repository supertokens/create-supertokens-app (24 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,967 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.