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./user-type-agent-experience)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./user-type-agent-experience"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./user-type-agent-experience/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./user-type-agent-experience"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./user-type-agent-experience.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.00786 |
| Opus 5.5 | $0.00000 | $0.00314 |
| Sonnet 5.5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
user-type-agent-experience 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent vs Buyer Experience (useIsAgent / agent role)
This app supports two distinct experiences:
- Buyer / regular user: Uses the app to buy/manage their own home search and workflow.
- Real-estate agent: Uses the app to manage/support other users (clients) buying homes (agent dashboard, client selection, agent messaging flows, agent-only polling/routes).
Source of truth: agent identity
- Server:
user_rolesrow withrole = "agent". - API wire:
User.roles: string[]on profile and auth session payloads (nois_agentfield). - Client check:
userHasAgentRole(user)inClient/packages/utils/auth/userHasAgentRole.ts, oruseIsAgent()inClient/packages/hooks/store/useIsAgent.ts.
Client state: how it’s persisted and accessed
-
Auth store (preferred for UI decisions):
useAuthStore/useAuthStoreIntegration().user- The persisted
auth-storeincludesroles(notis_agent). - Best practice:
const isAgent = useIsAgent() - Inline alternative:
userHasAgentRole(useAuthStore.getState().user)
- The persisted
-
Session store meta:
useSessionStore().userMeta?.isAgent- Do not use this for gating/rendering (non-authoritative).
Naming conventions (be explicit)
- API / schema:
rolesarray; agent UX when"agent"is present. - Local UI boolean:
isAgent(camelCase) fromuseIsAgent()oruserHasAgentRole. - Route intent booleans: MUST be named by intent, not identity:
- ✅
isMessagingRoute,isCalendarRoute,isOnMessagingPage - ❌
isAgent = path.startsWith("/messaging")
- ✅
- Onboarding draft:
formData.primary_onboarding_role("buyer"|"agent"| …) from the first-screen role picker; sent to preferences write asprimary_onboarding_roleto grant the agent role. Do not use a legacyis_agentdemographics field.
Roles vs agent UX
- Use
roles(includes"agent") for agent identity, agent-only UX, and@require_agent_accesson the server. - Use other roles (
buyer,seller,brokerage_admin, etc.) for workspace shells and RoleGuard authorization.
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 · 60 lines · 0 tokens per session scan A afbfa22ac4b5
user-type-agent-experience 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 786 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
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.