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.
npx agentmods add instructions/bluewatercorp/riskmodels_api/claude-mdgit clone --depth 1 https://github.com/BlueWaterCorp/RiskModels_APIWhat 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 | $0.02316 | $0.02316 |
| Opus 5 | $0.01158 | $0.01158 |
| Sonnet 5 | $0.00463 | $0.00463 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
RiskModels_API CLAUDE.md 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RiskModels API — Agent Instructions
Claude Code quick path
Before adding SDK methods, HTTP clients, or MCP tools: run the RiskModels API discovery workflow — .cursor/skills/riskmodels-api-discovery/SKILL.md (MCP riskmodels_list_endpoints / riskmodels_get_schema / riskmodels_get_openapi_spec when available; else OPENAPI_SPEC.yaml and mcp/data/openapi.json).
| Doc | Use |
|---|---|
| OPENAPI_SPEC.yaml | REST contract |
| SEMANTIC_ALIASES.md | Metric names, batch column semantics |
| docs/ERM3_ZARR_API_PARITY.md | Zarr vs API field parity |
| SUPABASE_TABLES.md | DB tables used by DAL / SDK |
| .cursor/skills/risk-judgment-shape/SKILL.md | Interpretation boundary — qualifier wording lives in BWMACRO, not here |
Cross-repo edits (schemas, schema-paths.json, MCP copies, current_state.md): do not duplicate the checklist here — use docs/AGENTS_CROSS_REPO.md (synced from BWMACRO). End-user / analyst-facing pointers stay in AGENTS.md.
Project Identity
This is the RiskModels API — a Next.js + Supabase platform serving institutional equity risk analytics. The Python SDK (sdk/riskmodels/) provides the programmatic client, snapshot PDF pipeline, and visualization layer.
Snapshot Suite (Primary Focus)
We are building an Institutional PDF Snapshot Suite — eight 1-page reports across a 2×4 matrix: Risk (R1–R4) × Performance (P1–P4).
The R/P Matrix
| ID | Combo | Deliverable | Status |
|---|---|---|---|
| R1 | Current × Stock | Factor Risk Profile | ✅ Shipped |
| R2 | History × Stock | Risk Attribution Drift | Planned |
| R3 | Current × Portfolio | Concentration Mekko | Planned |
| R4 | History × Portfolio | Style Drift | Planned |
| P1 | Current × Stock | Return & Relative Perf | Planned (helpers ready) |
| P2 | History × Stock | Cumulative Performance | Planned (helpers ready) |
| P3 | Current × Portfolio | Return Contribution | Planned |
| P4 | History × Portfolio | Portfolio vs Benchmark | Planned |
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.
- 2d ago First seen · 161 lines · 2,316 tokens per session scan A 19ed8c45f250
RiskModels_API CLAUDE.md is an instructions file published in the GitHub repository BlueWaterCorp/RiskModels_API (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,316 tokens to every session, about $0.0116 per session on Opus 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.