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.
git clone --depth 1 https://github.com/yaniv-golan/affinity-sdkWrote 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.
[](https://agentmods.dev/rules/yaniv-golan/affinity-sdk/test-data-privacy)<a href="https://agentmods.dev/rules/yaniv-golan/affinity-sdk/test-data-privacy"><img src="https://agentmods.dev/badge/rules/yaniv-golan/affinity-sdk/test-data-privacy/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.
<a href="https://agentmods.dev/rules/yaniv-golan/affinity-sdk/test-data-privacy"><img src="https://agentmods.dev/badge/rules/yaniv-golan/affinity-sdk/test-data-privacy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00496 | $0.00496 |
| Opus 5.5 | $0.00198 | $0.00198 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (1 stars, last pushed 20d ago), licensed MIT. It adds 496 tokens to every session, about $0.0020 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.
Other cursor rules, from other repositories
executing-red-team-engagement-planning
Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.