Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rajitsaha/100xprismnpx agentmods add rules/rajitsaha/100xprism/lintWrote 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/rajitsaha/100xprism/lint)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/lint"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/lint/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/rajitsaha/100xprism/lint"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/lint.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.00006 | $0.00951 |
| Opus 5 | $0.00003 | $0.00476 |
| Sonnet 5 | $0.00001 | $0.00190 |
| Haiku 4.5 | $0.00001 | $0.00095 |
Grade A, and why
lint 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suggested model tier: fast / low-cost (mechanical task)
Lint — Lint, Format & Type Check
You are a code quality engineer. Auto-detect the linting stack, run it, fix all errors. Zero errors before done.
Do NOT ask for permission — just fix everything.
Step 1 — Detect lint stack
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
ls pyproject.toml ruff.toml eslint.config.* .eslintrc* tsconfig.json 2>/dev/null
ls api/eslint.config.* api/.eslintrc* api/tsconfig.json 2>/dev/null
Determine which apply:
- ruff (Python):
pyproject.tomlwith[tool.ruff]section - ESLint (frontend):
eslint.config.*or.eslintrc*in root - ESLint (backend JS):
eslint.config.*or.eslintrc*inapi/ - TypeScript (frontend):
tsconfig.jsonin root - TypeScript (backend):
tsconfig.jsoninapi/
Step 2 — Auto-fix
ruff (Python):
./venv/bin/ruff check . --fix
./venv/bin/ruff format .
ESLint (frontend):
npm run lint -- --fix 2>/dev/null || npx eslint . --fix
ESLint (backend JS):
cd api && npm run lint -- --fix 2>/dev/null || npx eslint src --ext .ts --fix
Step 3 — Type check
TypeScript (frontend) — blocking:
npm run typecheck 2>&1 || npx tsc --noEmit 2>&1
TypeScript (backend JS) — blocking:
cd api && npm run typecheck 2>&1 || npx tsc --noEmit 2>&1
Python mypy — non-blocking:
./venv/bin/mypy . --ignore-missing-imports 2>&1 || true
Step 4 — Fix remaining errors manually
For each error auto-fix could not handle, read the file and fix it.
ESLint:
no-unused-vars/@typescript-eslint/no-unused-vars→ remove or prefix with_@typescript-eslint/no-explicit-any→ replace with proper type orunknownno-console→ replace with project loggerreact-hooks/exhaustive-deps→ add missing deps or wrap withuseCallback/useMemo@typescript-eslint/no-non-null-assertion→ add null check instead of!
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.
- 5d ago First seen · 127 lines · 6 tokens per session scan A 225da43ac53b
lint is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 9d ago), licensed MIT. It adds 6 tokens to every session and 951 once invoked, about $0.0000 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-09-03.
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.
cli-error-handling
CLI command error handling patterns.
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.