Borrowing it
Nothing to install: this file belongs to JBorgia/signaltree. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JBorgia/signaltree/main/.cursorrulesgit clone --depth 1 https://github.com/JBorgia/signaltreeWrote 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/jborgia/signaltree/cursorrules)<a href="https://agentmods.dev/rules/jborgia/signaltree/cursorrules"><img src="https://agentmods.dev/badge/rules/jborgia/signaltree/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/jborgia/signaltree/cursorrules"><img src="https://agentmods.dev/badge/rules/jborgia/signaltree/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.04991 | $0.04991 |
| Opus 5.5 | $0.01996 | $0.01996 |
| Sonnet 5.5 | $0.00998 | $0.00998 |
| Haiku 4.5 | $0.00499 | $0.00499 |
Grade C, and why
cursorrules scanned grade C with 1 finding 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 2mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. ✅ Clean install: `rm -rf node_modules pnpm-lock.yaml && pnpm install` How it starts
The opening of the file, as written. The whole thing — 711 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SignalTree Repository Rules & Context
This file provides comprehensive context for AI assistants working on the SignalTree codebase.
Numbers in this file
Every measured figure here names the tool that regenerates it. If you are about
to state a size or a timing that is not in this file, run the generator — do not
recall it, and do not read it from artifacts/*.json, which is gitignored local
scratch that has already put stale figures into published docs. See AGENTS.md.
This file primes code generation, so a wrong number here becomes wrong numbers in other people's repositories.
Repository Overview
SignalTree: Reactive JSON for Angular. JSON branches, reactive leaves.
No actions. No reducers. No selectors. Type-safe, dot-addressable state where data stays plain and reactivity stays invisible.
Core Philosophy:
-
JSON Branches — Your state paths look like JSON.
$.user.profile.settings -
Reactive Leaves — Leaf nodes are signals you read and write.
tree.$.name() -
No Mechanics — No actions, reducers, or selectors. Just data that reacts.
-
Lazy by Design — Signals created only where accessed. Minimal runtime footprint.
-
Language: TypeScript
-
Framework: Angular (for ng-forms, demo)
-
Package Manager: pnpm
-
Monorepo Tool: Nx
-
Build Tools: Rollup (packages & guardrails), Angular CLI (demo)
-
Testing: Vitest
-
Linting: ESLint
-
License: Apache-2.0
Architecture
Monorepo Structure
signaltree/
├── packages/ # All npm packages
│ ├── core/ # Main package with recursive typing
│ ├── ng-forms/ # Angular forms integration
│ ├── guardrails/ # Dev-only performance monitoring (Rollup build)
│ ├── shared/ # Internal shared utilities (PRIVATE - not published)
│ ├── types/ # Internal TypeScript types (PRIVATE)
│ └── utils/ # Internal utilities (PRIVATE)
├── apps/
│ └── demo/ # Demo application (Angular 19+)
├── scripts/ # Build, release, and validation scripts
├── dist/ # Build output (gitignored)
└── docs/ # Documentation
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.
- 2mo ago First seen · 711 lines · 4,991 tokens per session scan C 766f23ebcbb1
cursorrules is a cursor rule published in the GitHub repository JBorgia/signaltree (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,991 tokens to every session, about $0.0200 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).