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/yaniv-golan/affinity-sdk/test-data-privacygit clone --depth 1 https://github.com/yaniv-golan/affinity-sdkWhat 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.00496 | $0.00496 |
| Opus 5 | $0.00248 | $0.00248 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
test-data-privacy 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.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test data privacy
Real Affinity CRM data is sometimes used during local diagnosis (incident transcripts, repro screenshots, audit-log excerpts). Treat every real company name, real person name, and real deal/opportunity name that surfaces during diagnosis as confidential.
Rules
- Never embed real company, person, deal, or opportunity names from diagnosis material into committed artifacts. This includes: source code, tests, fixtures, docstrings, comments, CHANGELOG entries, COMPATIBILITY notes, SKILL.md examples, plan files that get checked in, commit messages, PR titles/bodies, and issue descriptions.
- Allowed exceptions — legitimate author/maintainer identity in package metadata only:
pyproject.tomlauthors,mcp/mcpb.confMCPB_AUTHOR_NAME,*.claude-plugin/plugin.jsonauthor,.claude-plugin/marketplace.jsonowner blocks. Do not introduce a real name into any new context outside of those exact metadata fields. - Use placeholders for examples and test data. Prefer
Jane Doe/John Doefor people,Acme Corp/Acme Holdingsfor companies,Example Dealfor deals/opportunities. Use<full name>when the example needs to be obviously a placeholder in a docstring or hint message. - Numeric IDs from real records are also sensitive. Replace with obviously-fake IDs (
12345,999,111111111) in tests, examples, and docs. - Incident transcripts shared in chat are diagnosis-only. Extract the technical pattern (e.g. "agent retried after exit 2 → partial-commit") but never the entity names. Refer to the incident with a generic label like "the recent agent-driven intake incident" rather than naming a tenant, deal, or person.
- When in doubt, ask before committing anything that quotes from a real Affinity record.
Auditing
When reviewing diffs or committing changes, scan for accidental leaks with:
git diff --cached | rg -i '<real-name-pattern>' && echo "ABORT: real name in staged diff"
If a leak is discovered post-commit but pre-push, rewrite history before pushing. If already pushed, surface immediately to the maintainer.
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 · 28 lines · 496 tokens per session scan A 5d197645b74a
test-data-privacy is a cursor rule published in the GitHub repository yaniv-golan/affinity-sdk (0 stars, last pushed 1mo ago), licensed MIT. It adds 496 tokens to every session, about $0.0025 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
no-summaries
Do not create summary documents, completion reports, or documentation files unless explicitly requested by the user.
api-patterns
Cursor rule "api-patterns" from LeadMagic/smartlead-mcp-server, covering 🏗️ smartlead api development patterns & best practices, 🎯 quick reference, 🔥 most important patterns, 🏗️ smartlead api client architecture and 🛠️ base client pattern.
SmartLead MCP TypeScript Standards
TypeScript coding standards, patterns, and best practices for the SmartLead MCP Server.
bmad-master
This rule is triggered when the user types @bmad-master and activates the BMad Master Task Executor agent persona.
bmad-orchestrator
This rule is triggered when the user types @bmad-orchestrator and activates the BMad Master Orchestrator agent persona.
dev
This rule is triggered when the user types @dev and activates the Full Stack Developer agent persona.