import-new-api

import-new-api is a skill for Claude Code from jentic/jentic-one. It costs 142 tokens per session (3,529 once invoked), scanned C, original, Apache-2.0.

A workflow for adding a vendor API that is not yet listed in the jentic-public-apis catalogue. It creates or finds an OpenAPI specification, optionally loads it into a local registry, publishes it to a reusable repository, and opens an import issue.

In plain words
What is it for?
Use it when given a vendor name or API documentation URL and you need to prepare its API description, local import, public repository copy, and tracking issue.
Why use it?
It provides a defined path when an API has no existing catalogue entry, so an agent can use the API locally and prepare it for community inclusion.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it when given a vendor name or API documentation URL and you need to prepare its API description, local import, public repository copy, and tracking issue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jentic/jentic-one/import-new-api
Install

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.

Any agent
npx skills add jentic/jentic-one --skill import-new-api
Clone the repo
git clone --depth 1 https://github.com/jentic/jentic-one

Made for: Claude Code.

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.

agentmods badge for import-new-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/jentic/jentic-one/import-new-api/github.svg)](https://agentmods.dev/skills/jentic/jentic-one/import-new-api)
Your own site
<a href="https://agentmods.dev/skills/jentic/jentic-one/import-new-api"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/import-new-api/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.

agentmods 80×15 button for import-new-api

Your own site · 80×15
<a href="https://agentmods.dev/skills/jentic/jentic-one/import-new-api"><img src="https://agentmods.dev/badge/skills/jentic/jentic-one/import-new-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,529 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00142 $0.03529
Opus 5.5 $0.00057 $0.01412
Sonnet 5.5 $0.00028 $0.00706
Haiku 4.5 $0.00014 $0.00353

Measured 19d ago against content hash 2fbeeedb9ed5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

import-new-api scanned grade C with 2 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 19d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/import-openapi-specs

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

code=$(curl -s -o /dev/null -w "%{http_code}" -L "$RAW"); [ "$code" = 200 ] && break; sleep $((i*5))
skills/import-new-api/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Import a New API (spec → local registry → import-openapi-specs repo → import issue)

Import an API that is not yet in jentic-public-apis: generate an OpenAPI spec from the vendor's docs, optionally import it into the local Jentic registry first (so the user's agent can execute it immediately), then publish it to the user's single reusable public repo import-openapi-specs and open the import issue that drives it into the community catalog.

This is the greenfield counterpart to contribute-spec-fix (which fixes a spec already in the catalog). Use contribute-spec-fix when the vendor already exists; use this skill when it does not.

Target: $ARGUMENTS (a vendor name like firecrawl, or a URL to the vendor's API docs). If only a company name is given, find its public API docs by searching for <company> API documentation.

Prerequisites

  • gh CLI authenticated (gh auth status) with repo scope. Note which account is active — the spec repo is created there and its raw links must resolve publicly.
  • No local jentic-public-apis checkout needed — the vendor-existence check runs against GitHub via gh.
  • For the optional local-first step only: a running Jentic control plane and a registered agent identity (jentic doctor confirms a resolvable identity with a usable token; jentic api GET /me shows what you can do).

Steps

1. Confirm the vendor is NOT already in the catalog (hard gate)

Check the live repo, not a local checkout:

gh api "repos/jentic/jentic-public-apis/contents/apis/openapi" --paginate \
  --jq '.[].name' | grep -i '<vendor-guess>'

Try the real domain (firecrawl.dev), bare name (firecrawl), and obvious variants (with and without subdomains: api.foo.com vs foo.com). If a matching vendor directory exists, STOP and tell the user — re-importing produces a duplicate, and the import workflow hard-fails on an existing version directory anyway. Point them at contribute-spec-fix if they meant to fix the existing spec, or offer a genuinely-absent alternative.

Read the full file on GitHub · 268 lines

Changes

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.

  1. 19d ago Changed 2fbeeedb9ed5
  2. 27d ago Changed · -2 lines ce2f34571435
  3. 1mo ago Changed 5bd5ebc7f360
  4. 1mo ago First seen · 270 lines · 142 tokens per session scan C 2850ea1c0446

Subscribe to this mod's changes

import-new-api is a skill published in the GitHub repository jentic/jentic-one (190 stars, last pushed 2d ago), licensed Apache-2.0. It adds 142 tokens to every session and 3,529 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.