com-example-strategy-PaymentStrategy

com-example-strategy-PaymentStrategy is a cursor rule for Cursor from PIsberg/vibetags. It costs 0 tokens per session (178 once invoked), scanned A, original, MIT.

Rules for a payment interface that uses the Strategy pattern, where each payment method has its own implementation.

In plain words
What is it for?
Implementing and validating payments made by credit card, PayPal, cryptocurrency, or other payment methods, including returning a transaction ID after success.
Why use it?
They keep payment methods separate and easier to change instead of putting every payment type into one large conditional block.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/pisberg/vibetags/com-example-strategy-paymentstrategy
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-strategy-PaymentStrategy

README.md
[![agentmods](https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-strategy-paymentstrategy.svg)](https://agentmods.dev/rules/pisberg/vibetags/com-example-strategy-paymentstrategy)
Your own site
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-strategy-paymentstrategy"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-strategy-paymentstrategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00178
Opus 5 $0.00000 $0.00089
Sonnet 5 $0.00000 $0.00036
Haiku 4.5 $0.00000 $0.00018

Measured 4d ago against content hash 4cc1f9e5c82c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

com-example-strategy-PaymentStrategy 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 4d 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-strategy-PaymentStrategy.mdc · 20 lines

What it actually says

Rules for PaymentStrategy

Context & Focus

  • Focus: Follow the Strategy pattern strictly. Each payment method should be a separate strategy class implementing this interface.
  • Avoid: Monolithic if-else chains, hard-coded payment logic, single class handling all payment types

Rules for method executePayment

  • Instruction: Implement payment execution specific to the payment method (credit card, PayPal, cryptocurrency, etc.). Return transaction ID on success.

Rules for method validatePaymentMethod

  • Instruction: Validate payment method specific data (card numbers, email addresses, wallet addresses, etc.). Return true if valid, false otherwise.
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. 4d ago First seen · 20 lines · 0 tokens per session scan A 4cc1f9e5c82c

Subscribe to this mod's changes

com-example-strategy-PaymentStrategy is a cursor rule published in the GitHub repository PIsberg/vibetags (15 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 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-08-30.