What is repo-sync-enforcer?

A workflow guide for keeping schemas, API descriptions, machine-readable data, and documentation synchronized across several related repositories. It identifies which repository and file should be treated as the source for each asset.

Use it when changing JSON schemas, schema path mappings, OpenAPI files, MCP data, or related tracking and API documentation.

It prevents different copies of the same API definition or documentation from drifting apart and causing misleading or inconsistent changes.

How BlueWaterCorp/RiskModels_API configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to BlueWaterCorp/RiskModels_API. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BlueWaterCorp/RiskModels_API/main/.agents/skills/repo-sync/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/BlueWaterCorp/RiskModels_API

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bluewatercorp/riskmodels_api/repo-sync/github.svg)](https://agentmods.dev/skills/bluewatercorp/riskmodels_api/repo-sync)

Your own site

<a href="https://agentmods.dev/skills/bluewatercorp/riskmodels_api/repo-sync"><img src="https://agentmods.dev/badge/skills/bluewatercorp/riskmodels_api/repo-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bluewatercorp/riskmodels_api/repo-sync"><img src="https://agentmods.dev/badge/skills/bluewatercorp/riskmodels_api/repo-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,679 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00047	$0.01679
Opus 5.5	$0.00019	$0.00672
Sonnet 5.5	$0.00009	$0.00336
Haiku 4.5	$0.00005	$0.00168

Measured 2mo ago against content hash 2fe659f8a46b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.agents/skills/repo-sync/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repo Sync Enforcer

When editing schemas, OpenAPI specs, MCP data, or tracking docs across the RiskModels repos, follow this workflow to prevent drift.

Step 1: Identify Canonical Repo

Asset	Canonical Repo	Path
JSON schemas	RiskModels_API	`mcp/data/schemas/*.json`
schema-paths.json	RiskModels_API (edit first)	`mcp/data/schema-paths.json`
capabilities.json	RiskModels_API	`mcp/data/capabilities.json`
openapi.json (generated)	RiskModels_API	`mcp/data/openapi.json`
OPENAPI_SPEC.yaml	RiskModels_API	`OPENAPI_SPEC.yaml`
CHANGELOG	RiskModels_API	`CHANGELOG.md`
MASTER_BACKLOG.md (engineering OSOT)	BWMACRO	`docs/ceo/MASTER_BACKLOG.md`
current_state.md (API narrative)	BWMACRO	`docs/api_roadmap/current_state.md`

Path note: canonical is RiskModels_API/mcp/ (singular). The portal mirror lives at Risk_Models/riskmodels_net/mcp-server/ (different subdir name). Don't confuse them — copying into the wrong path creates phantom drift that passes diff -q only if both sides have the same subdir name.

Step 2: New Schema Workflow

Create/edit schema in RiskModels_API/mcp/data/schemas/
Add to schema-paths.json in RiskModels_API:
```
"/schemas/NEW_SCHEMA-v1.json"
```
Copy schema to Risk_Models (or merge to RiskModels_API main and rely on Sync MCP data to Risk_Models in that repo — requires REPO_ACCESS_TOKEN with write to Risk_Models; see docs/AGENTS_CROSS_REPO.md):
```
cp RiskModels_API/mcp/data/schemas/NEW_SCHEMA-v1.json \
   Risk_Models/riskmodels_net/mcp-server/data/schemas/
```
Update schema-paths.json in Risk_Models (same entry)
Add CHANGELOG entry in RiskModels_API
Update MASTER_BACKLOG.md (terse burn-down row) and current_state.md (narrative / tables) in BWMACRO when format, gap, or endpoint surface changes

Full artifact resync (when portal drift is broader than one schema)

Read the full file on GitHub · 117 lines

Changes

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 · 117 lines · 47 tokens per session scan A 2fe659f8a46b

Subscribe to this mod's changes

repo-sync-enforcer is a skill published in the GitHub repository BlueWaterCorp/RiskModels_API (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 1,679 once invoked, about $0.0002 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.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

RiskModels_API: Skill for Claude Code