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./ci-gates)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./ci-gates"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./ci-gates/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./ci-gates"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./ci-gates.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.00652 |
| Opus 5.5 | $0.00000 | $0.00261 |
| Sonnet 5.5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
ci-gates 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Gates (Prevent Drift After Split)
Goal
Once RN exists, drift between web and shared code starts immediately. Run the gates locally before opening or merging PRs; CI lint runs on a weekly schedule (see Workflow below).
Required Client Gates (local + weekly CI)
These must pass before merge (run locally; CI re-runs weekly on Monday):
- Typecheck —
pnpm typecheck(e.g.tsc -p apps/web/tsconfig.json). No type errors. - Lint —
pnpm lint(ESLint including silverkey rules andeslint-plugin-tailwindcssconflicting-class detection, then Stylelint on CSS inputs). No errors. - Cycle check —
pnpm lint:cycles(e.g. madge circular dependency check). No cycles inapps/webandpackages. - Formatting —
pnpm format:check(Prettier). No unformatted files. - File size — Enforced via ESLint rule
silverkey/max-lines-hard(e.g. max 500 lines per file). Part ofpnpm lint. The intent is to flag oversized files; prefer addressing cyclomatic complexity and real maintainability over splitting into many tiny files just to satisfy the limit (see code-organization: complexity over line count, avoid file fragmentation).
Workflow
- Single entry point:
scripts/ci/run-all-linters.shruns all linters for a scope (client|server|all). Fix phase runs first (Client:pnpm run fix; Server:ruff check --fix+ruff format), then checks — same order in CI and locally. Server: everyServer/scripts/lint/lint_*.pythen each executableServer/scripts/lint/lint_*.sh(sorted). Client: every executableClient/scripts/lint.d/*.sh(sorted), thenpnpm check. New linters: add a matching file underServer/scripts/lint/; no workflow or root script edit required. - CI:
.github/workflows/lint.ymlruns the root script for client and server (two jobs) on a weekly schedule (Monday 09:00America/New_York, same as.github/dependabot.ymlweekly-all) and onworkflow_dispatch. It does not run on every push or pull request.ci_web.yml(prod web deploy) does not run lint or tests.
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 · 34 lines · 0 tokens per session scan A 48442c2fb969
ci-gates 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 652 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
vios-testing-cicd
Testing and CI/CD conventions for VIOS.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
build-tags
The shipped build tag set is spelled in several places that move together.
do-no-shortcuts
Stop before every shortcut — do the proper path instead.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
testing-ci-rule
testing-ci-rule from DaunteEth/woofi-pro-mcp.