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 skills add lingxling/awesome-skills-cn --skill api-onboardinggit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/api-onboarding)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/api-onboarding"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/api-onboarding/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/skills/lingxling/awesome-skills-cn/api-onboarding"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/api-onboarding.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.00046 | $0.03075 |
| Opus 5.5 | $0.00018 | $0.01230 |
| Sonnet 5.5 | $0.00009 | $0.00615 |
| Haiku 4.5 | $0.00005 | $0.00308 |
Grade A, and why
api-onboarding 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer sk_test_YOUR_KEY" ... This is a copy
98% identical to api-onboarding — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reducing Time-to-First-API-Call
When to Use
Use this skill when you need reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: "API...
The time between a developer discovering your API and successfully making their first call is the most critical window in your entire developer journey. Every minute of friction here costs you potential users.
Overview
Time-to-First-API-Call (TTFAC) is the single most predictive metric for developer adoption. Developers who succeed quickly become active users. Developers who struggle leave—often silently.
This skill covers:
- Measuring and optimizing TTFAC
- Removing authentication friction
- Creating effective sandbox environments
- Building interactive documentation
- Identifying and fixing common failure points
Before You Start
Review the developer-audience-context skill to understand:
- What's the typical technical sophistication of your developers?
- What tools and environments do they commonly use?
- What alternative products have they tried? What was their experience?
- What's their urgency level? (Evaluating vs. building immediately)
Your onboarding should meet developers where they are.
Understanding TTFAC
What TTFAC Measures
Time-to-First-API-Call measures the elapsed time from a developer's first interaction to their first successful API response. This includes:
- Discovery time: Finding the "Get Started" content
- Signup time: Creating an account
- Credential time: Obtaining API keys
- Setup time: Installing SDK, configuring environment
- Execution time: Running first request
- Success time: Receiving successful response
TTFAC Benchmarks
| Rating | TTFAC | Developer Experience |
|---|---|---|
| Excellent | < 5 min | "This is amazing" |
| Good | 5-15 min | "Pretty straightforward" |
| Acceptable | 15-30 min | "Got there eventually" |
| Poor | 30-60 min | "This is frustrating" |
| Failing | > 60 min | "I'll try something else" |
What ships with it
1 file 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.
- 19d ago First seen · 474 lines · 46 tokens per session scan A 449db96a19ee
api-onboarding is a skill published in the GitHub repository lingxling/awesome-skills-cn (321 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 3,075 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to api-onboarding, differing in 38 lines, and is treated as a copy.
Other skills, from other repositories
api-design
Design production-grade REST, GraphQL, gRPC, and Python library APIs with correct schemas, error contracts, auth, and versioning. Use when the user asks to design an API, define endpoints, create an OpenAPI/Swagger spec, design a GraphQL schema, build a gRPC service, model request/response with Pydantic, add…
content-modelling
Design CMS content models — content types, fields, editorial workflows, governance rules, and COPE (Create Once, Publish Everywhere) patterns — for structured, multi-channel publishing. Use when the user asks to design a content model, define content types in a CMS, structure fields for editorial content, plan a…
nodejs-development
Node.js development guidelines covering Payload CMS, Vue.js with TypeScript, and general TypeScript best practices.
dotnet
Guidelines for .NET backend development with C#, ASP.NET Core, and Entity Framework Core.
microservices
Guidelines for building production-grade microservices with FastAPI/Python and Go, covering serverless patterns, clean architecture, observability, and resilience.
voice-ai-realtime-agent
Expert guide for Ultra-Low Latency Conversational Voice AI (<300ms), WebRTC bidirectional streaming, OpenAI Realtime API, Gemini Multimodal Live Audio, LiveKit Agents, and Semantic VAD / Panduan ahli AI suara percakapan real-time berlatensi ultra-rendah.