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.
npx agentmods add rules/zapsign/api-mcp/testinggit clone --depth 1 https://github.com/ZapSign/api-mcpWhat 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 | $0.00000 | $0.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
testing 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.
What it actually says
Testing Conventions
Framework
- Vitest with
@cloudflare/vitest-pool-workers(runs in workerd runtime) - Config:
vitest.config.tsusingdefineWorkersConfig
File Locations
- Unit tests:
test/unit/**/*.test.ts - Integration tests:
test/integration/**/*.test.ts - Mock data:
test/mocks/zapsign-responses.ts
Test Naming
- Use
describe('module/function name', () => { ... }) - Use
it('should + expected behavior', () => { ... }) - Group by happy path, error cases, edge cases
Mock Conventions
- Mock
global.fetchfor API client tests - Mock
ZapSignClientmethods for tool tests - Use realistic data from
test/mocks/zapsign-responses.ts - Never mock the module under test
Assertions
- Prefer
expect(x).toBe(y)for primitives - Prefer
expect(x).toEqual(y)for objects - Prefer
expect(fn).toThrow(ErrorClass)for error testing - Always assert on error properties (code, statusCode, retryable)
Pre-commit
Run before every commit: npm run typecheck && npm run lint && npm test
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.
- yesterday First seen · 36 lines · 0 tokens per session scan A ea3b41a3a4a3
testing is a cursor rule published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 tokens. 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
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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.