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./documentation)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./documentation"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./documentation/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./documentation"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./documentation.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.00465 | $0.00465 |
| Opus 5.5 | $0.00186 | $0.00186 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
documentation 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
Documentation
- Single canonical tree: All SilverKey long-form prose lives under
documentation/at the repo root. Seedocumentation/README.mdanddocumentation/how-we-document.md. - Repo-root
docs/must not exist. Do not create it. If you see broken links todocs/, retarget todocumentation/runbooks/for Postgres/Redis/Celery ops. Creatingdocs/at repo root fails CI (scripts/ci/check-doc-placement.sh). - Hubs (Diataxis):
getting-started/,architecture/,features/,guides/,reference/,runbooks/,policies/,internal/. - As-built only: No roadmap or Planned design trees in-repo. Track planned work in Linear.
- Colocated exception only:
*/docs/inside vendor-owned subtrees (e.g.Server/app/services/docusign/docs/). - FORBIDDEN paths for new long-form guides: repo-root
docs/,Client/documentation/, ad-hoc long.mdin feature folders (usedocumentation/features/instead). - Lightweight READMEs: Major folders keep short READMEs that link into
documentation/. - Adding docs: Place under the correct hub; add a row to that hub’s README. Run
scripts/ci/check-doc-placement.shandscripts/ci/check-doc-links.sh(make check-docs). Skill:.cursor/skills/documentation-placement/SKILL.md. - Major feature or architecture change: documentation/internal/post-major-change-checklist.md and skill post-major-change-sync.
- Team-maintained exceptions (no surprise markdown):
AGENTS.md,CLAUDE.md,ARCHITECTURE.md,setup.md,.cursor/README.md,documentation/internal/**,.github/pull_request_template.md.
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 · 21 lines · 465 tokens per session scan A 9409c26eb996
documentation is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It adds 465 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-08-31.
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.