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/jaycewalzer1/SilverKey-Inc.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.
[](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./openapi-schema-organization)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./openapi-schema-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./openapi-schema-organization/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/jaycewalzer1/silverkey-inc./openapi-schema-organization"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./openapi-schema-organization.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.01008 |
| Opus 5.5 | $0.00000 | $0.00403 |
| Sonnet 5.5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
openapi-schema-organization 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAPI Schema Organization
File Structure
openapi/
├── openapi.yaml # Main spec with $ref to components
├── _onepath.yaml # Variant with paths included
├── _nopaths.yaml # Variant without paths
└── components/
└── schemas/
├── agent/ # Agent workspace schemas
│ ├── core/ # Core agent types
│ └── conversations/ # Conversation types
├── auth/ # Authentication schemas
├── calendar/ # Calendar and events
├── checklists/ # Task checklists
├── feed/ # Social feed
├── offers/ # Offer management
├── preferences/ # User preferences
├── search/ # Property search
│ ├── filters/ # Search filters
│ ├── properties/ # Property details
│ └── results/ # Search results
├── shared/ # Shared/common schemas
│ ├── core/ # Core shared types
│ └── chatbot/ # Chatbot types
└── user/ # User-related schemas
├── favorites/ # Favorite homes
├── not-interested/ # Not interested homes
├── profile/ # User profile
└── todos/ # User todos
Naming Conventions
File Names
- PascalCase:
UserProfile.yaml,SearchByPolygonRequest.yaml - Match schema name: File name = schema name
- Descriptive suffixes: Request/Response for API DTOs
Schema Organization
Group schemas by domain, then by subdomain:
# ✅ CORRECT: Organized by domain
components/schemas/user/profile/UserProfile.yaml
components/schemas/user/favorites/FavoriteHomesResponse.yaml
components/schemas/search/filters/SearchByPolygonRequest.yaml
# ❌ WRONG: Flat structure
components/schemas/UserProfile.yaml
components/schemas/FavoriteHomesResponse.yaml
components/schemas/SearchByPolygonRequest.yaml
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 · 148 lines · 0 tokens per session scan A 550cf2aec8be
openapi-schema-organization is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,008 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-09-08.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
selectools-providers
Rules for working with LLM provider adapters in selectools.