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/coeusyk/inference-xWrote 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/coeusyk/inference-x/api-contracts)<a href="https://agentmods.dev/rules/coeusyk/inference-x/api-contracts"><img src="https://agentmods.dev/badge/rules/coeusyk/inference-x/api-contracts/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/coeusyk/inference-x/api-contracts"><img src="https://agentmods.dev/badge/rules/coeusyk/inference-x/api-contracts.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.00211 | $0.00211 |
| Opus 5.5 | $0.00084 | $0.00084 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
api-contracts 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.
What it actually says
API contract rules
- Treat request and response schemas as public contracts.
- Avoid breaking field names or response structure after an endpoint is introduced.
- If a contract must change, introduce a new version or clearly isolate the change behind a new endpoint.
- Keep OpenAI-compatible behavior where planned for
/v1/chat/completions. - Ensure error responses are consistent and predictable.
- Add or update contract tests whenever endpoint behavior changes.
Phase 1 contract
Required endpoints:
POST /v1/chat/completionsGET /health
Phase 1 expectations:
- one configured vLLM-backed model
- typed request validation
- typed response formatting
- clear error handling for configuration, model load, and inference failures
Contract design rules
- Prefer additive change over breaking change.
- Keep optional fields optional; do not make them required later without versioning.
- Return machine-readable status information where useful.
- Document examples in
README.mdordocs/ARCHITECTURE.mdwhen endpoints stabilize.
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 · 28 lines · 211 tokens per session scan A 5eab52dbbdd3
api-contracts is a cursor rule published in the GitHub repository coeusyk/inference-x (2 stars, last pushed 19d ago), licensed MIT. It adds 211 tokens to every session, about $0.0008 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.
Other cursor rules, from other repositories
go-api-handlers
Use authorization functions for apps.
use-frontend-api-client
Generated API client usage.
fastapi-pydantic
You are an expert in Python, FastAPI, and scalable API development.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
python
Python best practices and patterns for modern software development with Flask and SQLite.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.