tests

tests is a cursor rule for Cursor from Edison-Watch/Custom-MCPs. It costs 317 tokens per session, scanned A, original, MIT.

A project rule for writing Python tests with pytest, a Python testing tool, using the repository's expected test structure and shared setup.

In plain words
What is it for?
Use it when adding features or tests, especially when creating files or folders under the tests directory.
Why use it?
It keeps new tests consistent with the existing test suite and reminds developers to test new features.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding features or tests, especially when creating files or folders under the tests directory.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/edison-watch/custom-mcps/tests
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/Edison-Watch/Custom-MCPs

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 tests

README.md
[![agentmods](https://agentmods.dev/badge/rules/edison-watch/custom-mcps/tests/github.svg)](https://agentmods.dev/rules/edison-watch/custom-mcps/tests)
Your own site
<a href="https://agentmods.dev/rules/edison-watch/custom-mcps/tests"><img src="https://agentmods.dev/badge/rules/edison-watch/custom-mcps/tests/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 tests

Your own site · 80×15
<a href="https://agentmods.dev/rules/edison-watch/custom-mcps/tests"><img src="https://agentmods.dev/badge/rules/edison-watch/custom-mcps/tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 317 This file is loaded in full into every session.
When invoked 317 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.00317 $0.00317
Opus 5.5 $0.00127 $0.00127
Sonnet 5.5 $0.00063 $0.00063
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

tests 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/tests.mdc · 42 lines

What it actually says

Writing tests

Whenever implementing a new feature, always encourage the user to write a test.

Tests are written using pytest. To add a new test, create a new file/directory in the tests/ directory. Ensure, that whenever you create a new directory in the tests/ directory, you also add a tests/.../__init__.py to the directory so python can recognize the test directory.

Test structure

Look at below example for how you should write tests.

from tests.test_template import TestTemplate, slow_test, nondeterministic_test
from common import global_config

class TestSkeleton(TestTemplate):
    # Initialize shared variables here for all tests
    @pytest.fixture(autouse=True)
    def setup_shared_variables(self, setup):
        # Initialize shared attributes here
        pass

    # Actual test code here
    # Possibly @slow_test or @nondeterministic_test
    def test_function(self):
        # Any actual test code here
        assert True

Few things to note:

  • Inherit from TestTemplate (see tests/test_template.py) for proper test setup
  • Use self.config for test configuration (loaded from tests/config.yaml)
  • Prefix tests with test_ and use @slow_test or @nondeterministic_test decorator for slow and/or nondeterministic tests
  • Never use unittest, always use pytest
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 · 42 lines · 317 tokens per session scan A 93a0f55fd6f5

Subscribe to this mod's changes

tests is a cursor rule published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed 18d ago), licensed MIT. It adds 317 tokens to every session, about $0.0013 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.