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/tanstack/devtools/jsdocgit clone --depth 1 https://github.com/TanStack/devtoolsWhat 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.00072 | $0.00072 |
| Opus 5 | $0.00036 | $0.00036 |
| Sonnet 5 | $0.00014 | $0.00014 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
jsdoc 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.
What it actually says
Your rule content
- The JSDoc in this repo is important as it gets converted to markdown docs for the website, so it should read like documentation.
- Don't include
@params,@args,@template, or@returnsin our jsdoc
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 · 10 lines · 72 tokens per session scan A 49f4d9bb9f86
jsdoc is a cursor rule published in the GitHub repository TanStack/devtools (493 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session, about $0.0004 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
test-running
When running tests, use the --watch false flag to avoid watch mode.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
backend
Backend development rules for TT Studio - AI model management backend.
project-context
Core project context — tech stack, folder structure, and global conventions.
context-management
Context window management — prevents AI from losing track during long sessions.