test-coverage-100

test-coverage-100 is a cursor rule for Cursor from adobe/spacecat-api-service. It costs 290 tokens per session, scanned A, original, Apache-2.0.

A testing rule that requires all executable JavaScript source code to have complete line, branch, statement, and function coverage. Coverage measures how much of the code tests actually run.

In plain words
What is it for?
Use it after changing files under src/ by running npm test and adding tests under test/ until all coverage checks pass.
Why use it?
It prevents source changes from being treated as finished when important paths are untested. The required test command matches the one used by continuous integration, the automated checks run for submitted code.

Cursor rule for Cursor ✓ vendor

Written for Cursor: installed under .cursor/.

Good fit Use it after changing files under src/ by running npm test and adding tests under test/ until all coverage checks pass.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/adobe/spacecat-api-service/test-coverage-100
About the project

SpaceCat API Service is an HTTP API for working with SpaceCat data, including a server-side proxy for the Semrush AIO API and a PostgreSQL-backed data service. Developers and operators use it to access and run the Edge Delivery services data system.

adobe/spacecat-api-service · 10 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/adobe/spacecat-api-service

Made for: Cursor.

Wrote 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.

agentmods badge for test-coverage-100

README.md
[![agentmods](https://agentmods.dev/badge/rules/adobe/spacecat-api-service/test-coverage-100/github.svg)](https://agentmods.dev/rules/adobe/spacecat-api-service/test-coverage-100)
Your own site
<a href="https://agentmods.dev/rules/adobe/spacecat-api-service/test-coverage-100"><img src="https://agentmods.dev/badge/rules/adobe/spacecat-api-service/test-coverage-100/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.

agentmods 80×15 button for test-coverage-100

Your own site · 80×15
<a href="https://agentmods.dev/rules/adobe/spacecat-api-service/test-coverage-100"><img src="https://agentmods.dev/badge/rules/adobe/spacecat-api-service/test-coverage-100.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 290 This file is loaded in full into every session.
When invoked 290 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00290 $0.00290
Opus 5.5 $0.00116 $0.00116
Sonnet 5.5 $0.00058 $0.00058
Haiku 4.5 $0.00029 $0.00029

Measured 1mo ago against content hash 6ca50a473114, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-coverage-100 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.

.cursor/rules/test-coverage-100.mdc · 31 lines

What it actually says

Test coverage (100%)

This repo enforces 100% lines, branches, and statements for src/**/*.js via c8 and .nycrc.json (check-coverage: true).

After editing code under src/

  1. Run npm test (same command CI uses: c8 + mocha). Do not mark the task done if coverage fails.
  2. If coverage fails, add or extend unit tests in test/ (mirror src/ layout) until thresholds pass. Prefer exercising real code paths over c8 ignore comments unless the project already uses them for a case that cannot be tested.

Faster iteration (optional)

To check one source file against its test file:

npx c8 --check-coverage --lines 100 --branches 100 --statements 100 --functions 100 \
  --include='src/path/to/file.js' --src src \
  mocha test/path/to/matching.test.js --timeout 15000

Replace paths to match the module you changed.

Do not

  • Assume coverage is fine without running npm test after substantive src/ edits.
  • Leave new functions or branches untested when they carry business logic.
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. 1mo ago First seen · 31 lines · 290 tokens per session scan A 6ca50a473114

Subscribe to this mod's changes

test-coverage-100 is a cursor rule published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed 25d ago), licensed Apache-2.0. It adds 290 tokens to every session, about $0.0012 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.