react tsx lint contract

A set of coding rules for React components written in JSX or TSX, where markup is embedded in JavaScript or TypeScript. It covers Hooks, component structure, element syntax, list keys, and lint checks.

In plain words
What is it for?
Use it when editing React, TSX, or JSX files, especially when changing Hooks, lists, component definitions, JSX elements, or lint-related code.
Why use it?
It helps prevent common React mistakes and keeps edited components compatible with the repository's lint rules. It also requires checking the relevant lint target after changes.

Instructions file for GitHub Copilot

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 instructions/borgius/kanban-lite/react-tsx
Clone the repo
git clone --depth 1 https://github.com/borgius/kanban-lite

Made for: GitHub Copilot.

Per session 209 This file is loaded in full into every session.
When invoked 209 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00209 $0.00209
Opus 5 $0.00105 $0.00105
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

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

Security

Grade A, and why

react tsx lint contract 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.

.github/instructions/react-tsx.instructions.md · 19 lines

What it actually says

React / TSX lint contract

  • When editing React or TSX, write code that passes eslint.config.mjs without adding new inline eslint-disable comments.
  • Follow Hooks rules and prefer fixing dependency arrays over suppressing react-hooks/exhaustive-deps.
  • Prefer self-closing JSX for elements without children.
  • Prefer boolean props like disabled over disabled={true}.
  • Avoid useless fragments when a single element or expression is enough.
  • Do not use array indexes as React keys when a stable identifier exists.
  • Avoid defining components inside other components unless there is a clear, local reason.
  • After React or TSX edits, run the relevant lint target and fix the violations introduced by your change.
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 · 19 lines · 209 tokens per session scan A 444305321d49

Subscribe to this mod's changes

react tsx lint contract is an instructions file published in the GitHub repository borgius/kanban-lite (6 stars, last pushed 3mo ago), licensed MIT. It adds 209 tokens to every session, about $0.0010 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-31.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens