Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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/skills/jentic/jentic-api-scorecard/jentic-api-improve)<a href="https://agentmods.dev/skills/jentic/jentic-api-scorecard/jentic-api-improve"><img src="https://agentmods.dev/badge/skills/jentic/jentic-api-scorecard/jentic-api-improve.svg" alt="Measured on agentmods" 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.00124 | $0.21553 |
| Opus 5 | $0.00062 | $0.10776 |
| Sonnet 5 | $0.00025 | $0.04311 |
| Haiku 4.5 | $0.00012 | $0.02155 |
Grade A, and why
jentic-api-improve scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
python3 -c "import sys, urllib.request; urllib.request.urlretrieve(sys.argv[1], sys.argv[2])" "<literal-value-of-$0>" "./.jentic-improve-work/spec.<EXT>" How it starts
The opening of the file, as written. The whole thing — 855 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAPI Improve
Overview
Improve the OpenAPI document at the provided path or URL ($0) for AI-readiness. The target document is the first argument passed to this skill. An optional second argument ($1) specifies the output directory; when omitted, the outputs land in the input file's own directory (see "Output"). An optional mode selects how far the skill may alter the spec — non-breaking (default), summary-description, or full (see "Change-Scope Modes"); when omitted, mode is non-breaking and the skill behaves exactly as it did before modes existed.
This skill runs a baseline score that includes diagnostics, identifies weak dimensions and actionable diagnostics, then applies targeted improvements — either inline for simple fixes or via a subagent for multi-iteration loops. In the default non-breaking mode improvements are non-breaking (they only add to the spec, never change or remove existing paths, parameters, or response shapes); summary-description is narrower still, and full opts into breaking changes bounded by the no-dimension-regression guard. Every run produces both an improved spec and an OpenAPI Overlay (the reusable delta), and every run runs an oasdiff breaking-change check against the original.
If the jentic-api-scorecard skill is installed, you can use it for a more thorough initial and/or final analysis before starting improvements or within iterations.
Reference files in references/ are large and should be loaded lazily — only read a reference file when its content is specifically needed (e.g. to understand scoring formulas or overlay structure). Do not preload all references at once.
For Claude Code users: copy agents/jentic-api-improve.md (from the repo root) to your project's .claude/agents/ or ~/.claude/agents/ to enable the declarative subagent definition. This is optional — the skill works without it by spawning subagents via inline brief.
Change-Scope Modes
The skill runs in one of three modes, selected by a mode argument (e.g. mode=full) or an equivalent instruction in the invocation. When no mode is given, the mode is non-breaking — identical to the skill's behavior before modes existed. The mode bounds which edits the skill may apply and how the oasdiff breaking-change check reacts; it threads through to the subagent via the brief's "Change-scope mode" field.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 855 lines · 124 tokens per session scan A 8a599b3ca2d8
jentic-api-improve is a skill published in the GitHub repository jentic/jentic-api-scorecard (21 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 21,553 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
fastapi-expert
Expert-level FastAPI development for high-performance Python APIs with async support. Use when the user mentions Python, API, async, REST, OpenAPI, or Pydantic, or when the task involves FastAPI Features.
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…
api-documenter-v2
This public intake copy packages plugins/antigravity-awesome-skills/skills/api-documenter from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.