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./code-style)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./code-style"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-style/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./code-style"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./code-style.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.00721 | $0.00721 |
| Opus 5.5 | $0.00288 | $0.00288 |
| Sonnet 5.5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
code-style 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.
SilverKey coding conventions
Company context: silverkey-context.mdc and pitch-and-fundraising.mdc. Lint details: linting.mdc. CI gates: ci-gates.mdc.
Stack
| Area | Stack |
|---|---|
| Client | pnpm 9, Node 20+, React (Vite web) + React Native (Expo), TypeScript, Zustand, Vitest |
| Server | Python 3.10–3.13, Flask, SQLAlchemy, Celery/Redis, pytest, ruff/mypy |
| Contract | OpenAPI 3.1 in openapi/ — regenerate types; never hand-edit generated files |
| Layout | Thin apps (Client/apps/*), fat packages (Client/packages/*) — thin-app-architecture.mdc |
Commits and PRs
- Commit format:
[LINEAR-ID] short description(e.g.[SK-142] Add partner placement prefill params). - PR description: Link the Linear ticket URL or ID; summarize what changed and why.
- Do not commit: secrets, API keys,
.env, partner deal terms, or credentials files.
Architecture (pointers)
- Client layers: frontend-architecture.mdc — components → hooks → config/api → services; no fat apps.
- OpenAPI changes: openapi-workflow.mdc — edit spec,
make openapi/make openapi-verify. - Security: security.mdc — tokens in memory + sessionStorage; mask PII in logs.
Partner and money flows
Code touching partner placement, payments, or brokerage revenue must be:
- Boring and auditable — clear names, explicit branches, minimal cleverness.
- RESPA-documented — comment block per respa-compliance.mdc.
- Logged — partner exposure and money-adjacent events traceable.
Done means verified
Before claiming complete:
| Scope | Minimum check |
|---|---|
| Client | pnpm typecheck, pnpm lint, relevant tests; full gate: pnpm check or make check-client |
| Server | targeted pytest; repo lint: make lint or ./scripts/ci/run-all-linters.sh server |
| OpenAPI | make openapi-verify when HTTP shapes changed |
| Both | ./scripts/ci/run-all-linters.sh all or make lint for cross-cutting PRs |
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 · 721 tokens per session scan A 194764bbe83e
code-style is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It adds 721 tokens to every session, about $0.0029 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
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.