agentmods.dev

coding-standards

Coding rules for TypeScript, a programming language that adds type checking to JavaScript.

In plain words
What is it for?
They help write and review TypeScript functions, files, types, constants, comments, and logging.
Why use it?
They set consistent limits for code structure, naming, complexity, error handling, and type safety.

Cursor rule for Cursor

1 3d ago A scan 338 tokens original MIT
View the source file ZapSign/api-mcp
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/zapsign/api-mcp/coding-standards
Clone the repo
git clone --depth 1 https://github.com/ZapSign/api-mcp

Made for: Cursor.

Per session 338 This file is loaded in full into every session.
When invoked 338 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.00338 $0.00338
Opus 5 $0.00169 $0.00169
Sonnet 5 $0.00068 $0.00068
Haiku 4.5 $0.00034 $0.00034

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

Security

Grade A, and why

coding-standards 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.

.cursor/rules/coding-standards.mdc · 37 lines

What it actually says

Coding Standards

Structural Rules

  • Early return pattern: always. Guard clauses at the top.
  • No else after return. No else blocks at all.
  • No switch statements: use object maps (Record<string, handler>).
  • Maximum 2 levels of nesting. Extract to a function if deeper.
  • Cyclomatic complexity < 10 per function.
  • Cognitive complexity < 10 per function.
  • Maximum function length: 40 lines (excluding type signatures and JSDoc).
  • Single responsibility: each function does ONE thing.

Type Safety

  • No any: use unknown + type guards.
  • No as type assertions (except untyped library interfaces, with comment).
  • No silent catch blocks: re-throw, log, or return an error.
  • Use as const objects for finite value sets (NOT TypeScript enums).

Naming

  • Files: kebab-case (create-document.ts)
  • Types/Interfaces/Classes: PascalCase (ZapSignDocument)
  • Functions/Variables: camelCase (listDocuments)
  • Constants: UPPER_SNAKE_CASE (MAX_RETRY_ATTEMPTS)
  • Const value objects: PascalCase name + keys (DocumentStatus.Pending)
  • Log events: snake_case, past tense, max 35 chars (document_created)

Comments

  • English only. Explain WHY, never WHAT.
  • No narration comments.
  • JSDoc only on exported functions with @param, @returns, @throws.
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 · 37 lines · 338 tokens per session scan A a9405176cfcc

Subscribe to this mod's changes

coding-standards is a cursor rule published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 338 tokens to every session, about $0.0017 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.

Code reviewLanguages
Related

Other cursor rules, from other repositories

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

typescript

Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens