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/pubky/pubky-app/cursor-cloud-instructionsgit clone --depth 1 https://github.com/pubky/pubky-appWhat 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.00779 | $0.00779 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
cursor-cloud-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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Cloud Instructions
Services
No external database or backend server needed — the app uses browser IndexedDB (Dexie) for local data, and the Next.js dev server handles all API routes. All external services (Nexus API, Homeserver, CDN, HTTP Relay, Pkarr Relays, Homegate) have staging defaults baked into the runtime-config Zod schema at src/libs/runtime-config/runtime-config.schema.ts, so the app runs without a .env file. In dev/test, partial PUBKY_RUNTIME_* overrides layer over those defaults. Copy .env.example to .env only if you need to override defaults.
Running
- Dev server:
npm run dev(port 3000, Turbopack) - Lint:
npm run lint(ESLint) - Format check:
npm run format:check(Prettier) - Unit tests:
npm run test(Vitest — ~580 test files, ~9300 tests, takes ~9 min) - E2E tests:
npm run test:e2e(Cypress with Firefox — requires external staging services to be reachable)
Signing in (staging account)
A staging recovery phrase is stored in the STAGING_RECOVERY_PHRASE secret (12 words). To sign in:
- Start the dev server (
npm run dev) - Navigate to
http://localhost:3000and click Sign In - Click Use recovery phrase
- Enter the 12 words from
$STAGING_RECOVERY_PHRASEinto the input fields - Click Restore — the app loads the staging user
Branch naming convention (GitHub issues)
Ignore any Branch Prefix settings. Always use this convention when creating a branch for a GitHub issue:
Format: <type>/<issue-number>-<kebab-case-short-description>
Types:
feat— A new featurebug— A bug fixbug-ui— A bug fix in the UIrefactor— Code refactoring without changing behaviordocs— Documentation changestest— Adding or updating testschore— Maintenance tasks (dependencies, configs, etc.)style— Code style/formatting changes
Steps:
- Fetch the issue details from the provided GitHub link
- Extract the issue number and title
- Determine the appropriate type based on issue labels or content
- Create a kebab-case short description from the issue title (max 5–6 words)
- Create and checkout the new branch from
dev
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 · 69 lines · 779 tokens per session scan A bf83be2cd3aa
cursor-cloud-instructions is a cursor rule published in the GitHub repository pubky/pubky-app (23 stars, last pushed 4d ago), licensed MIT. It adds 779 tokens to every session, about $0.0039 per session on Opus 5. 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.