api-contract-docs

A set of project rules for keeping public API documentation and OpenAPI descriptions aligned with code changes. OpenAPI is a standard format for describing web APIs.

In plain words
What is it for?
Use it when changing a public API, its documentation, its OpenAPI files, or related MCP tool schemas.
Why use it?
It prevents endpoint, parameter, and response changes from leaving the guides, generated README, and API specifications out of date.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/pricewatcha/pricewatcha-api/api-contract-docs
Clone the repo
git clone --depth 1 https://github.com/pricewatcha/pricewatcha-api

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 242 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00242
Opus 5 $0.00000 $0.00121
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

Measured yesterday against content hash 66271dcec6a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-contract-docs 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 yesterday.

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.

.cursor/rules/api-contract-docs.mdc · 21 lines

What it actually says

Public API contract updates

Canonical guides live in docs/. Do not edit README.md by hand.

After any semantic change to endpoints, query params, or response fields:

  1. Edit the matching file under docs/ (and docs/changelog.md).
  2. Run python scripts/build_readme.py.
  3. Update openapi/openapi.yaml (GitHub contract). Query params need a description.
  4. Update ../price_tracker/app/api/v1/openapi_spec.py (live GET /openapi.json).
  5. Run ../price_tracker/scripts/sync_api_docs.sh and commit app/api_docs/.
  6. If an MCP tool is affected: mcp-server/src/tools/*.ts and mcp/tools.schema.json.

Checks: python scripts/build_readme.py --check and python scripts/verify_openapi_query_descriptions.py.

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.

  1. yesterday First seen · 21 lines · 0 tokens per session scan A 66271dcec6a8

Subscribe to this mod's changes

api-contract-docs is a cursor rule published in the GitHub repository pricewatcha/pricewatcha-api (1 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 242 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.