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/adobe/spacecat-api-service/test-coverage-100git clone --depth 1 https://github.com/adobe/spacecat-api-serviceWhat 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.00290 | $0.00290 |
| Opus 5 | $0.00145 | $0.00145 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
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 2d 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
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/
- Run
npm test(same command CI uses:c8+ mocha). Do not mark the task done if coverage fails. - If coverage fails, add or extend unit tests in
test/(mirrorsrc/layout) until thresholds pass. Prefer exercising real code paths overc8 ignorecomments 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 testafter substantivesrc/edits. - Leave new functions or branches untested when they carry business logic.
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.
- 2d ago First seen · 31 lines · 290 tokens per session scan A 6ca50a473114
test-coverage-100 is a cursor rule published in the GitHub repository adobe/spacecat-api-service (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 290 tokens to every session, about $0.0014 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.
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.