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./monorepo)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./monorepo"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./monorepo/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./monorepo"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./monorepo.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.00278 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
monorepo 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
Monorepo and Tooling
- Prefer workspace-aware commands; the Client workspace uses
pnpmscripts fromClient/package.json(e.g.pnpm lint,pnpm typecheck). - Do not edit files in
Client/dist/,Client/coverage/(generated outputs). - Follow documented structure in
documentation/: seedocumentation/README.mdanddocumentation/how-we-document.md. Client architecture and package layout are indocumentation/architecture/andClient/ARCHITECTURE.md. For Thin App (Fat Packages), seedocumentation/architecture/thin-app-architecture.mdandthin-app-architecture.mdc. - Keep configuration changes in
Client/config/where applicable (ESLint, Prettier, PostCSS) and root configs for Vite/Tailwind/TS. - For CI or local tasks, use existing scripts: dev, build, test, lint, format. Doc checks:
make check-docsor./scripts/ci/check-doc-placement.sh+./scripts/ci/check-doc-links.sh. - Markdown creation: Follow
documentation.mdcfor canonical placement and forbidden paths.
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 · 16 lines · 0 tokens per session scan A cff012639669
monorepo 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 278 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
changesets
Changeset format and bump rules enforced by CI.
project-context
Current repository context, commands, and documentation authority.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
git_rules
When asked to interact with git, github or project management tooling (jira, linear, asana etc).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.