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/workflowgit 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.01235 | $0.01235 |
| Opus 5 | $0.00617 | $0.00617 |
| Sonnet 5 | $0.00247 | $0.00247 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
workflow 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow (TDD, layered, docs-aware)
This file is alwaysApply: true, so it loads in every Cursor session (same priority as the top-level project rules).
openapi-to-cli (ocli) is a TypeScript CLI that turns OpenAPI/Swagger specs into runtime commands. The user-facing surface is the ocli binary, .ocli/ config dir, and profiles.ini. Tests live next to source in tests/ and run with Jest. Behavior is specified by tests; the README documents the public CLI contract.
New features (TDD)
When the user asks for a new feature (words like "feature", "add", "implement", "фича", "добавить"), follow this order. Do not skip steps.
- Plan: outline the steps for the change (modules to touch, tests to add). Use a task list if it spans more than 2-3 steps.
- Failing test first: add or extend a test in
tests/<module>.test.ts. The test must describe the new behavior indescribe/itand fail for the right reason. - Confirm red: run only that test:
npx jest tests/<module>.test.ts -t "<title>". Confirm it fails as expected. - Implement: write the minimum code in
src/that makes the test pass. Follow @architecture.mdc and @code-style.mdc. When adding new classes, follow @implementation-order.mdc - lower layer first. - Confirm green: re-run the same test; it must pass.
- Full suite:
npm test. All tests must be green. Fix regressions before moving on. - Build check:
npm run buildto confirmtscis clean (no type errors). - Docs: update
README.mdwhenever any of the following change: CLI flags, command names, profile fields,.ocli/layout, BM25 search behavior, supported OpenAPI/Swagger features, or the benchmark numbers. If you changed observable CLI output (--help, error messages, exit codes), update the relevant section of the README. Theexamples/skill-ocli-api.mdandskills/ocli-api/SKILL.mdmust stay aligned with the documented agent workflow. - Report: brief summary of files touched, tests added, suite result.
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 · 75 lines · 1,235 tokens per session scan A 5393e1231c27
workflow is a cursor rule published in the GitHub repository EvilFreelancer/openapi-to-cli (256 stars, last pushed 11d ago), licensed MIT. It adds 1,235 tokens to every session, about $0.0062 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).