Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewaynpx agentmods add rules/alphabitcore/nexus-gateway/code-doc-lockstepWrote 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/alphabitcore/nexus-gateway/code-doc-lockstep)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/code-doc-lockstep"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/code-doc-lockstep/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/alphabitcore/nexus-gateway/code-doc-lockstep"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/code-doc-lockstep.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.01054 | $0.01054 |
| Opus 5.5 | $0.00422 | $0.00422 |
| Sonnet 5.5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
code-doc-lockstep 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code / Doc Lockstep (BINDING)
Docs are the single source of truth. If code drifts from a doc, the code is wrong — fix the doc to match reality if needed, but never ship code that contradicts its doc.
The rule
When a PR touches code in a region covered by a doc, every matching doc MUST be updated in the same commit. The doc isn't a follow-up; it's part of the change. This applies to every doc tree:
| Doc tree | What changes here trigger an update |
|---|---|
docs/developers/architecture/** |
internal mechanics, data flow, contracts between services |
docs/users/features/** |
user-visible UI surface, admin features, agent UX |
docs/users/api/openapi/** |
request/response schemas, new/renamed/removed endpoints |
docs/operators/ops/runbooks/** |
deployment steps, recompute scripts, operational procedures |
docs/developers/specs/** |
Epic / Story acceptance criteria as scope evolves |
A single code change typically touches multiple doc trees. Examples:
- New admin endpoint → OpenAPI spec + architecture doc + feature doc (if UI surface) + runbook (if ops procedure).
- Cost-stamping change →
cost-estimation-architecture.md+prod-deploy-data-changes.md(if historical recompute) + feature doc for the Traffic drawer (if visible breakdown changes). - Provider adapter codec change →
provider-adapter-architecture.md+ feature doc if visible to admins. - Schema migration →
cost-estimation-architecture.md(if cost columns) ORthing-config-sync-architecture.md(if shadow) + runbook if any historical data fix is part of the PR.
How it's enforced
scripts/check-doc-lockstep.mjs runs on the PR diff against origin/main. If any code file matches a configured glob and none of the mapped docs are in the diff, the check fails with the file list + which docs were expected.
The mapping lives at scripts/doc-lockstep.config.mjs. Each entry is one or more code globs plus one or more required docs. Adding a new entry is easy — edit the config and open the PR.
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 · 69 lines · 1,054 tokens per session scan A a1f2aa85cd5e
code-doc-lockstep is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,054 tokens to every session, about $0.0042 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-30.
Other cursor rules, from other repositories
solana-security
Solana Security Standard (SOL-0XX) - flag and fix Solana/Anchor security bugs.
recipe_author
How to author a recipe in ks-cookbook.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.
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.