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/BlueWaterCorp/RiskModels_APIWrote 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/bluewatercorp/riskmodels_api/repo-sync-enforcer)<a href="https://agentmods.dev/rules/bluewatercorp/riskmodels_api/repo-sync-enforcer"><img src="https://agentmods.dev/badge/rules/bluewatercorp/riskmodels_api/repo-sync-enforcer/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/bluewatercorp/riskmodels_api/repo-sync-enforcer"><img src="https://agentmods.dev/badge/rules/bluewatercorp/riskmodels_api/repo-sync-enforcer.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.00834 |
| Opus 5.5 | $0.00000 | $0.00334 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
repo-sync-enforcer 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 2mo 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.
Cross-Repo Sync Rules
This rule applies when editing schemas, OpenAPI specs, MCP data, or tracking docs. BWMACRO is the single source of truth for AI instructions across three related repos.
Repo Roles
| Repo | Role | Key Paths |
|---|---|---|
| BWMACRO | AI instructions + operational backlog | docs/ceo/MASTER_BACKLOG.md, docs/api_roadmap/current_state.md, docs/api_roadmap/next_steps.md |
| RiskModels_API | Canonical API surface | OPENAPI_SPEC.yaml, mcp/data/schemas/*.json, schema-paths.json, examples/, CHANGELOG.md |
| Risk_Models | User portal & dashboard (riskmodels.net). MCP schema consumer. No longer the canonical public API. | riskmodels_net/mcp-server/data/schemas/, riskmodels_net/mcp-server/data/schema-paths.json |
Core Rules (Always Enforce)
-
Schemas are canonical ONLY in RiskModels_API
New or updated JSON schemas (e.g.estimate-v1.json) must be created/edited inRiskModels_API/mcp/data/schemas/. -
Copy new schemas to Risk_Models
After adding a schema in RiskModels_API, manually copy to Risk_Models:cp RiskModels_API/mcp/data/schemas/NEW_SCHEMA.json Risk_Models/riskmodels_net/mcp-server/data/schemas/ -
Update schema-paths.json in BOTH repos
Add the new schema path toschema-paths.jsonin:RiskModels_API/mcp/data/schema-paths.jsonRisk_Models/riskmodels_net/mcp-server/data/schema-paths.json
-
Changelog in RiskModels_API
Add an entry toRiskModels_API/CHANGELOG.mdfor new endpoints, schemas, or format params. -
Roll up narrative status: When adding endpoints, schemas, formats, or closing gaps:
- Add a terse row or update an existing lettered item in
docs/ceo/MASTER_BACKLOG.md(engineering burn-down OSOT). - Keep
docs/api_roadmap/current_state.mdaligned for diagrams, Data Endpoints table, and MCP-facing narrative — avoid duplicating long sprint prose in both places unless both need the same wording for different audiences.
- Add a terse row or update an existing lettered item in
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.
- 2mo ago First seen · 69 lines · 0 tokens per session scan A 304ea87248af
repo-sync-enforcer is a cursor rule published in the GitHub repository BlueWaterCorp/RiskModels_API (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 834 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-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.