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/webjsdev/webjsWrote 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/webjsdev/webjs/cursorrules)<a href="https://agentmods.dev/rules/webjsdev/webjs/cursorrules"><img src="https://agentmods.dev/badge/rules/webjsdev/webjs/cursorrules/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/webjsdev/webjs/cursorrules"><img src="https://agentmods.dev/badge/rules/webjsdev/webjs/cursorrules.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.02016 | $0.02016 |
| Opus 5.5 | $0.00806 | $0.00806 |
| Sonnet 5.5 | $0.00403 | $0.00403 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
cursorrules 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules: webjs app
You are working on a webjs app, an AI-first, no-build, web-components-first framework. Read AGENTS.md for the full API reference and CONVENTIONS.md for project-specific conventions before writing any code. When AGENTS.md doesn't cover what you need, the full hosted docs are at https://webjs.dev/docs.
Persistence + scaffold rules (non-negotiable)
- Use Drizzle + SQLite for data, never JSON files. It's already wired up
(
db/schema.server.ts,db/connection.server.ts,npm run db:generate+npm run db:migrate). For ANY data the app stores (todos, posts, messages, products, comments…), define a Drizzle table. NEVER createdata/*.json,db.json, or any JSON file as a fake database. NEVER use module-scope arrays / Maps as a substitute. NEVER use localStorage for app data. These are project conventions in CONVENTIONS.md (a JSON file used as a database resets on reload and cannot scale). - The scaffold is reference, not the final product. Replace
app/page.ts, the exampleUsermodel, the example users module, etc. with the app the user actually asked for. Don't ship "Hello from " as the deliverable. - Only three templates exist:
webjs create <name>(default full-stack),--template api,--template saas. The CLI rejects any other--templatevalue. Pick:- Any product UI (todo, blog, dashboard, marketplace, social…) → default
- HTTP/JSON API only, no UI →
--template api - Auth / login / signup / SaaS →
--template saas
Before starting ANY work
FIRST, before writing any code:
- Run
git branch --show-currentto check the branch.- If on main/master: STOP. Ask the user which branch to use, or create
one with
git checkout -b feature/<name>. - If on a feature branch: verify it matches the current task. Ask if unsure.
- If on main/master: STOP. Ask the user which branch to use, or create
one with
- Sync with parent:
git fetch origin && git log HEAD..origin/main --oneline- If upstream has new commits:
git rebase origin/mainbefore starting. - Resolve any conflicts before proceeding with the task.
- If upstream has new commits:
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 · 108 lines · 2,016 tokens per session scan A 8ee86975065d
cursorrules is a cursor rule published in the GitHub repository webjsdev/webjs (27 stars, last pushed 7d ago), licensed MIT. It adds 2,016 tokens to every session, about $0.0081 per session on Opus 5.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
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-barrel-files
Avoid barrel files and unnecessary re-exports.
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
interface-factory-pattern
Interface-based design with factory functions (keep classes private).
explicit-opt-in-over-diagnostics
Prefer requiring explicit opt-in over emitting diagnostics on intentional user paths.