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./silverkey-context)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./silverkey-context"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./silverkey-context/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./silverkey-context"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./silverkey-context.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.00476 | $0.00476 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
silverkey-context 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.
What it actually says
SilverKey company context
Canonical context lives in this rule for company-level constraints and in pitch-and-fundraising.mdc for investor/deck language. Engineering quickstart: AGENTS.md.
RESPA reflex
When designing or reviewing partner-facing features (placement, marketplace, referrals, lender/title/insurance surfacing, agent compensation tied to partners):
- Assume RESPA Section 8 applies.
- Prefer brokerage-level marketplace placement over buyer-personalized steering.
- Flag compliance risks explicitly; link respa-compliance.mdc for code in scoped paths.
Real partners only
Use actual partners and facts from this rule and pitch-and-fundraising.mdc. Do not invent MSAs, logos, or signed deals.
| Partner | Fact |
|---|---|
| Better | Signed MSA: $3K + $1,500/user on launch |
| eXp | Pilot committed — Rob & Kim's team |
Live data over guessing
| Topic | Source |
|---|---|
| Financials, balances, runway | Mercury MCP (read-only) |
| Roadmap, tickets, status, planned product work | Linear MCP — do not track future work in repo markdown |
| Code, branches, PRs | GitHub MCP |
| Team threads | Slack MCP |
If MCP is unavailable, say so and mark figures TBD — do not fabricate.
Communication (Jayce)
- Direct, diagnostic feedback — name the problem, not vague praise.
- Concrete rewrites when suggesting copy or code changes.
- Explain what changed and why in summaries and PR-facing text.
- No fluff, no jargon-stuffing; specific numbers and partner names where they belong.
Fundraising and pitch
When editing pitch/deck/investor markdown, follow pitch-and-fundraising.mdc. Tagline verbatim unless explicitly iterating: "The operating system unlocking home transactions."
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 · 48 lines · 476 tokens per session scan A 84f11765a1c7
silverkey-context is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It adds 476 tokens to every session, about $0.0019 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-08.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.