com-example-testing-PaymentFixturesTest

com-example-testing-PaymentFixturesTest is a cursor rule for Cursor from PIsberg/vibetags. It costs 107 tokens per session, scanned A, original, MIT.

A set of rules for testing payment code with shared payment fixtures. It requires tests to compare exact minor-unit values, such as cents, rather than formatted currency strings.

In plain words
What is it for?
It is for writing and reviewing payment tests that build requests through PaymentFixtures and assert on their stored numeric amounts.
Why use it?
It prevents tests from creating payments inconsistently or passing because of formatting differences. This keeps currency and amount handling consistent across the test suite.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for writing and reviewing payment tests that build requests through PaymentFixtures and assert on their stored numeric amounts.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pisberg/vibetags/com-example-testing-paymentfixturestest
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/PIsberg/vibetags

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 com-example-testing-PaymentFixturesTest

README.md
[![agentmods](https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-testing-paymentfixturestest/github.svg)](https://agentmods.dev/rules/pisberg/vibetags/com-example-testing-paymentfixturestest)
Your own site
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-testing-paymentfixturestest"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-testing-paymentfixturestest/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 com-example-testing-PaymentFixturesTest

Your own site · 80×15
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-testing-paymentfixturestest"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-testing-paymentfixturestest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 This file is loaded in full into every session.
When invoked 107 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.00107 $0.00107
Opus 5.5 $0.00043 $0.00043
Sonnet 5.5 $0.00021 $0.00021
Haiku 4.5 $0.00011 $0.00011

Measured 25d ago against content hash 925215c4824c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

com-example-testing-PaymentFixturesTest 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 25d 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.

examples/basic/.cursor/rules/com-example-testing-PaymentFixturesTest.mdc · 14 lines

What it actually says

Rules for PaymentFixturesTest

Context & Focus

  • Focus: Build payments through PaymentFixtures, never with the PaymentRequest constructor: the fixture is what keeps minor units and currency consistent across the suite
  • Avoid: Asserting on formatted amounts; assert on the minor-unit long
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. 25d ago First seen · 14 lines · 107 tokens per session scan A 925215c4824c

Subscribe to this mod's changes

com-example-testing-PaymentFixturesTest is a cursor rule published in the GitHub repository PIsberg/vibetags (25 stars, last pushed today), licensed MIT. It adds 107 tokens to every session, about $0.0004 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-09-21.