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/sybrew/troyWrote 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/sybrew/troy/javascript)<a href="https://agentmods.dev/rules/sybrew/troy/javascript"><img src="https://agentmods.dev/badge/rules/sybrew/troy/javascript/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/sybrew/troy/javascript"><img src="https://agentmods.dev/badge/rules/sybrew/troy/javascript.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.00275 |
| Opus 5.5 | $0.00000 | $0.00110 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
javascript 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
Follow the JavaScript rules in @.github/instructions/javascript.instructions.md when editing JavaScript files.
After editing unminified src/troy-server/library/js sources, run the minify skill. Do not create, edit, read, grep, search, or git diff *.min.js or *.min.css, including after minify exit code 0.
Read .local/minify/permission.txt with an explicit path (Grep/Glob cannot see .local/). Never invent flags. If the file does not exist, prompt. If you cannot prompt and no permissions exist, skip minification altogether and ask at the end of the chat. After the user replies with both flags, write those two lines (JS=True/JS=False and CSS=True/CSS=False). If JS=False, do not prompt again, and do not clone or minify JS. If JS=True and .local/minify/babel-tsf/run.js is missing, clone https://github.com/theseoframework/babel-tsf into .local/minify/babel-tsf and run npm install there. That public repo is the source of truth.
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 · 12 lines · 275 tokens per session scan A 91ac6b063d8c
javascript is a cursor rule published in the GitHub repository sybrew/troy (55 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 275 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-10-26.
Other cursor rules, from other repositories
generate-pr-description
This rule provides guidance for generating a pull request (PR) description in this repository.
woo-build
This rule provides guidance for building the WooCommerce plugin and watching for changes in the repository.
respira-wordpress
How to edit a live WordPress site through the Respira MCP server. Use when working on WordPress pages, posts, page builders (Elementor, Divi, Bricks, Gutenberg and others) or WooCommerce through respira tools.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.