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.
git clone --depth 1 https://github.com/ZapSign/api-mcpWrote 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/zapsign/api-mcp/coding-standards)<a href="https://agentmods.dev/rules/zapsign/api-mcp/coding-standards"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/coding-standards/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/zapsign/api-mcp/coding-standards"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/coding-standards.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.00338 | $0.00338 |
| Opus 5.5 | $0.00135 | $0.00135 |
| Sonnet 5.5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
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 1mo 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.
What it actually says
Coding Standards
Structural Rules
- Early return pattern: always. Guard clauses at the top.
- No
elseafterreturn. Noelseblocks at all. - No
switchstatements: 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: useunknown+ type guards. - No
astype assertions (except untyped library interfaces, with comment). - No silent catch blocks: re-throw, log, or return an error.
- Use
as constobjects 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.
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.
- 1mo ago First seen · 37 lines · 338 tokens per session scan A a9405176cfcc
coding-standards is a cursor rule published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 338 tokens to every session, about $0.0014 per session on Opus 5.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.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).