cursorrules

A repository rule set that defines the project's coding conventions in one place. The description does not include the specific conventions.

In plain words
What is it for?
Use it when working in the repository to follow its local conventions, after checking the rule definitions for the details.
Why use it?
It gives coding agents a shared source for repository-specific rules instead of repeating them in every task. The available information does not show what those rules are.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/toddagriscience/nightcrawler/cursorrules
Clone the repo
git clone --depth 1 https://github.com/toddagriscience/nightcrawler

Made for: Cursor.

Per session 323 This file is loaded in full into every session.
When invoked 323 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00323 $0.00323
Opus 5 $0.00161 $0.00161
Sonnet 5 $0.00065 $0.00065
Haiku 4.5 $0.00032 $0.00032

Measured yesterday against content hash 968a31699405, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

apps/site/.cursorrules · 30 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 30 lines · 323 tokens per session scan A 968a31699405

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository toddagriscience/nightcrawler (11 stars, last pushed 2d ago), with no licence file. It adds 323 tokens to every session, about $0.0016 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.