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/jaycewalzer1/SilverKey-Inc.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.
[](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./respa-compliance)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./respa-compliance"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./respa-compliance/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/jaycewalzer1/silverkey-inc./respa-compliance"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./respa-compliance.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.00000 | $0.00770 |
| Opus 5.5 | $0.00000 | $0.00308 |
| Sonnet 5.5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
respa-compliance 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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RESPA compliance (partner & settlement services)
Company context: silverkey-context.mdc + pitch-and-fundraising.mdc for approved narrative language.
Section 8 (summary)
RESPA prohibits kickbacks and unearned fees for referrals to settlement services (mortgage, title, insurance, etc.). SilverKey must not implement flows that look like: agent/brokerage steers buyer → partner pays agent/brokerage per referral.
SilverKey model (compliant threading)
- Brokerage hosts a placement marketplace; partners pay for access/placement, not per-buyer referral to an agent.
- Revenue to the brokerage is a technology platform fee, not a referral fee for steering a specific buyer.
- Surfacing is brokerage- or workflow-level (e.g. checklist integration, admin partner config), with auditable exposure — not opaque agent kickbacks.
Required: RESPA comment block
Any function that selects, ranks, orders, or exposes partners to users must include a block like this directly above the function:
/**
* RESPA: <one sentence — e.g. brokerage-configured checklist embed; no per-buyer referral fee;
* partner pays platform placement; exposure logged via <event/hook>>.
*/
Python: use an equivalent docstring block.
Required: auditable partner exposure
Every partner exposure event (render, click-through to partner, embed open) must be traceable:
- Prefer structured logging via
packages/logger(client) orServer/logger(backend). - Include: partner id/slug, surface (e.g.
checklist.close.concierge), transaction/workspace context if applicable, timestamp. - Do not log PII beyond what product already allows; mask per security.mdc.
Patterns
Good
- Rev-share partner placements at checklist/workflow level — admin-configured URLs via
PartnerTransactionIntegration/partner_placements; exposure logged; not agent referral fees. - Admin partners section — brokerage configures which partners appear; changes are admin-auditable.
- Financing/insurance checklist items — transaction task completion, not "we recommend Lender X because Agent Y gets paid."
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.
- 1mo ago First seen · 74 lines · 0 tokens per session scan A 2c90a2a49d54
respa-compliance is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 770 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-08.
Other cursor rules, from other repositories
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
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.