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/testing)<a href="https://agentmods.dev/rules/zapsign/api-mcp/testing"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/testing/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/testing"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/testing.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.00000 | $0.00286 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.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 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
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.
- 1mo ago 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 7d 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
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.