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./post-major-change-sync)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./post-major-change-sync"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./post-major-change-sync/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./post-major-change-sync"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./post-major-change-sync.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.00556 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
post-major-change-sync 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post–major change: docs and Cursor sync
When a change is cross-cutting (new product modes, routing shells, auth/workspace model, OpenAPI contract, import/layer conventions, or repo structure), treat documentation + Cursor artifacts as part of the same deliverable as the code.
When this applies
- New or renamed route shells, dashboards, or navigation contracts (web/mobile).
- Workspace / identity UX shifts (
useActiveWorkspace, allowed workspaces, session persistence). - OpenAPI schema or codegen changes that affect client/server types.
- New always-on constraints or ESLint/package-structure rules (rare — see
.cursor/README.mdalways-on cap). - New repeatable workflows that engineers or agents should follow (prefer a skill under
.cursor/skills/).
Checklist (do not skip)
Use the full checklist: documentation/internal/post-major-change-checklist.md.
Minimum bar before calling the work “done”:
documentation/— Add or update the relevant guide underdocumentation/ordocumentation/; add a row to that folder’sREADME.mdwhen it is a new long-form doc..cursor/rules/— If behavior is now constrained or patterned differently, update the smallest set of.mdcfiles (or add one scoped rule withglobs; do not increase always-on rule count without replacing an existing always-on rule — see.cursor/README.md).AGENTS.md/.cursor/README.md— Update only when onboarding or extension process changes.documentation/internal/cursor-audit-latest.md— Refresh the inventory table when rules, skills, or agents are added/removed/renamed.
Examples
// ✅ DO — Same PR or fast-follow: workspace shells land + `documentation/architecture/workspace-first-architecture.md` updated
// ❌ DON'T — Large routing refactor with no doc or rule touch; the next agent will re-derive intent from diff noise only
Long prose and file maps belong in documentation/, not in bloated .mdc bodies (see documentation.mdc).
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 · 42 lines · 0 tokens per session scan A 417e6df08d41
post-major-change-sync 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 556 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.