agentmods.dev

cursorrules

A set of project rules for developing the ZapSign MCP server, including its Node.js structure, coding style, testing approach, and command-running method. MCP is a standard way for AI agents to access tools and data.

In plain words
What is it for?
Use it while changing the ZapSign MCP server, especially when running terminal commands, writing JavaScript, organizing files, or executing Jest tests.
Why use it?
It gives the coding agent consistent instructions about how to edit, test, name, and run parts of the project.

Cursor rule for Cursor

1 3d ago A scan 298 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/cursorrules
Clone the repo
git clone --depth 1 https://github.com/ZapSign/api-mcp

Made for: Cursor.

Per session 298 This file is loaded in full into every session.
When invoked 298 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.00298 $0.00298
Opus 5 $0.00149 $0.00149
Sonnet 5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

Measured yesterday against content hash 0c206e37662f, 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.

docs/archive/api-mcp-v1/.cursorrules · 39 lines

What it actually says

Cursor Rules for MCP ZapSign Server Project

Terminal Command Execution

  • ALWAYS use WSL MCP executor for running terminal commands to avoid IDE hanging
  • Use mcp_mcp-wsl-exec_execute_command for shell commands instead of run_terminal_cmd
  • This prevents the IDE from hanging during long-running or complex commands

Project Structure

  • This is an MCP (Model Context Protocol) server project for ZapSign API integration
  • Uses ES modules ("type": "module" in package.json)
  • Node.js 18+ required
  • Jest testing framework with ES module support

Code Quality

  • Follow ESLint rules strictly
  • Use single quotes for strings
  • Add trailing commas where appropriate
  • Keep functions under 50 lines when possible
  • Add JSDoc comments for public functions

File Naming

  • Use exact names referenced in prompts
  • Respect folder structure when creating files
  • Create .sh scripts to create folders when needed

Testing

  • Run tests in background mode to avoid hanging
  • Use WSL MCP for npm commands and testing
  • Jest configuration is in jest.config.cjs for ES module compatibility

Docker

  • Use docker-compose-build.yml for local development
  • Run containerized commands via WSL MCP when possible

MCP Server

  • Supports both STDIO and SSE modes
  • All ZapSign API tools are implemented and operational
  • Health monitoring available at /health endpoint
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 · 39 lines · 298 tokens per session scan A 0c206e37662f

Subscribe to this mod's changes

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

Backend and APIsCode reviewTesting
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