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/thearnavrustagi/marketmenow/testinggit clone --depth 1 https://github.com/thearnavrustagi/marketmenowWhat 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.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 today.
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
- pytest + pytest-asyncio with
asyncio_mode = "auto". - Async tests are plain
async def test_...-- no decorator needed. from __future__ import annotationsin every test file.
Patterns
- Use
pytest.raises(ExceptionType)for expected exceptions, never try/except. - Use
tmp_pathfixture for any file-system tests (YAML, CSV, templates). - Assert on specific fields, not full model equality, to avoid brittle UUID/datetime comparisons.
- No mocking of Pydantic validation -- test it directly with
pytest.raises(ValidationError).
Mocks and Fixtures
- Mock adapters implement Protocol interfaces via structural subtyping. Never subclass or inherit from the Protocol.
- Content model factories live in
conftest.py(e.g.make_text_post(),make_video()). Prefer these over inline construction in tests. - A pre-built
AdapterRegistryfixture is available inconftest.py.
Naming
- Files:
test_{module}.pymatching the source module under test. - Functions:
test_{module}_{behavior}(e.g.test_normaliser_video_with_thumbnail).
No External I/O
- Tests must never call external APIs, send emails, or launch browsers.
- All network and I/O dependencies are replaced with in-memory mocks.
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.
- today First seen · 41 lines · 0 tokens per session scan A 4b9f74ff16b9
testing is a cursor rule published in the GitHub repository thearnavrustagi/marketmenow (132 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 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-09-01.
Other cursor rules, from other repositories
didclaw-project
DidClaw 仓库总则 — 整合期协作、目录、品牌与 Git 纪律.
didclaw-security
DidClaw 安全与类型 — Tauri 权限、IPC、供应链与 TypeScript 边界.
didclaw-client
Cursor rule "didclaw-client" from didclawapp-ai/didclaw, covering didclaw 客户端（lclaw-ui）, 技术栈, 常用命令（在 lclaw-ui/ 下）, 实现约定 and 发布相关（备忘）.
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.