scripts

A set of project rules for checking code and organizing reusable checks. Each concern directory contains its configuration, and each detector follows a shared lint function that returns a result.

In plain words
What is it for?
Use it to organize lint checks, keep rule implementations consistent, and place skill-specific scripts in their designated directories.
Why use it?
It defines one structure and checking interface for project rules, while generating policy-related rules from code.

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/nitra/7n-rules/scripts
Clone the repo
git clone --depth 1 https://github.com/nitra/7n-rules

Made for: Cursor.

Per session 18,195 This file is loaded in full into every session.
When invoked 18,195 The same file — it is already loaded in full.
Security scan A 1 finding. 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.18195 $0.18195
Opus 5 $0.09098 $0.09098
Sonnet 5 $0.03639 $0.03639
Haiku 4.5 $0.01819 $0.01819

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

Security

Grade A, and why

scripts scanned grade A 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 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

**Принцип** (ADR [260716-1354](../../docs/adr/260716-1354-внутрішній-паралелізм-lint-оркестратора.md)). `detectAll()` (`npm/scripts/lib/lint-surface/run-detectors.mjs`) виконує план у двох лейнах, не одним наївним `Promi
.cursor/rules/scripts.mdc · 519 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 · 519 lines · 18,195 tokens per session scan A 6df56f5944d7

Subscribe to this mod's changes

scripts is a cursor rule published in the GitHub repository nitra/7n-rules (2 stars, last pushed yesterday), with no licence file. It adds 18,195 tokens to every session, about $0.0910 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.