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 rules/evilfreelancer/openapi-to-cli/architecturegit clone --depth 1 https://github.com/EvilFreelancer/openapi-to-cliWhat 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.01404 | $0.01404 |
| Opus 5 | $0.00702 | $0.00702 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
architecture 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture of openapi-to-cli (ocli)
ocli is a TypeScript/Node CLI that converts OpenAPI/Swagger specs into runtime CLI commands. No code generation: at every invocation it loads a cached spec and builds command definitions on the fly.
Data flow
ocli profiles add <name> --api-base-url ... --openapi-spec ...
|
v
ConfigLocator -> .ocli/ dir (global or local)
|
v
ProfileStore -> profiles.ini (read/write/select)
|
v
OpenapiLoader -> fetches spec, caches under .ocli/specs/<profile>.json
|
v
OpenapiToCommands -> parses spec, applies include/exclude filters,
builds CliCommand[] (name, method, path, options, body schema)
|
v
CommandSearch (BM25) -> ranks commands by NL query or regex
|
v
cli.ts (yargs) -> resolves profile + spec, dispatches: profiles | use | commands | <toolName>
|
v
HttpClient (axios) -> performs the real HTTP request to API_BASE_URL
Components (mapping to src/)
config.ts-ConfigLocator. Finds.ocli/(global~/.ocli/, local in CWD), resolvesprofiles.inipaths.profile-store.ts-ProfileStore,Profile. Reads/writesprofiles.ini, tracks current profile, validates fields.openapi-loader.ts-OpenapiLoader. Loads spec from URL or local file, caches it to.ocli/specs/<profile>.json, refreshes on demand. Resolves external$refacross multi-file specs.openapi-to-commands.ts-OpenapiToCommands,CliCommand,CliCommandOption. Walks the spec, applies include/exclude filters, expands path-level params, resolves local$ref, builds command names with optional prefix, expandsenum/default/nullable/oneOfschema hints for--help.command-search.ts-CommandSearch. BM25 over(name, method, path, description, options[].name), plus regex fallback. Same engine used by bothocli commandsand any future agent skill.command-args.ts-findUnknownFlags,acceptsFreeFormBody,formatUnknownFlagsError. Validates parsed flags of a dynamic command againstCliCommand.options, suggests the closest declared name, and keeps the free-form body passthrough for body-capable operations whose spec declares no body.bm25.ts- tokenizer + BM25 scorer, no I/O.cli.ts-oclientry point. yargs command tree:profiles add|remove|list,use,commands, and dynamic per-spec commands. Builds theaxiosrequest from aCliCommand+ parsed args; injects auth, custom headers, server URL overrides.version.ts- generated byscripts/generate-version.jsduringprebuild. Do not edit by hand.
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.
- yesterday First seen · 91 lines · 1,404 tokens per session scan A 373afaac64a5
architecture is a cursor rule published in the GitHub repository EvilFreelancer/openapi-to-cli (256 stars, last pushed 11d ago), licensed MIT. It adds 1,404 tokens to every session, about $0.0070 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-30.
Other cursor rules, from other repositories
deno
You MUST import @std dependencies from jsr You MUST use latest versions of libraries when adding imports You must use type keyword when importing types.
typescript-coding-rule
It allows a subset of JSDoc tags. Most tags must occupy their own line, with the tag at the beginning of the line.
errors
ALWAYS use custom errors from src/errors.ts.
files
File organization and structure rules.
_code-rules-TypeScript
Apply when creating or editing TypeScript (.ts) files or shared TypeScript modules. Enforces typed, modular, readable code with strict formatting, naming, imports, configuration, validation, error handling, async patterns, and separation of concerns.
typescript
// Bad const data: any = JSON.parse(content).