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 skills/apideck-libraries/api-skills/apideck-codegennpx skills add apideck-libraries/api-skills --skill apideck-codegengit clone --depth 1 https://github.com/apideck-libraries/api-skillsWhat 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.00068 | $0.02072 |
| Opus 5 | $0.00034 | $0.01036 |
| Sonnet 5 | $0.00014 | $0.00414 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
apideck-codegen 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 2d 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.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apideck Code Generation Skill
Overview
Apideck publishes OpenAPI 3.x specifications for all unified APIs at https://specs.apideck.com/{api-name}.yml. These specs can be used with code generators to produce typed clients, models, server stubs, and documentation in any language.
IMPORTANT RULES
- ALWAYS prefer the official Apideck SDKs over generated clients. Code generation is for languages/frameworks not covered by official SDKs, or for custom model generation.
- ALWAYS use the latest spec from
https://specs.apideck.com/{api-name}.yml. Do not use cached or outdated specs. - USE the official SDKs for: TypeScript (
@apideck/unify), Python (apideck-unify), C# (ApideckUnifySdk), Java (com.apideck:unify), Go (sdk-go), PHP (sdk-php). - When generating clients, always configure authentication headers:
Authorization,x-apideck-app-id,x-apideck-consumer-id.
Available OpenAPI Specs
| API | Spec URL |
|---|---|
| Accounting | https://specs.apideck.com/accounting.yml |
| CRM | https://specs.apideck.com/crm.yml |
| HRIS | https://specs.apideck.com/hris.yml |
| File Storage | https://specs.apideck.com/file-storage.yml |
| ATS | https://specs.apideck.com/ats.yml |
| E-commerce | https://specs.apideck.com/ecommerce.yml |
| Issue Tracking | https://specs.apideck.com/issue-tracking.yml |
| SMS | https://specs.apideck.com/sms.yml |
| Lead | https://specs.apideck.com/lead.yml |
| Vault | https://specs.apideck.com/vault.yml |
| Webhook | https://specs.apideck.com/webhook.yml |
| Connector | https://specs.apideck.com/connector.yml |
All specs are also available on GitHub: https://github.com/apideck-libraries/openapi-specs
OpenAPI Generator
Installation
# npm
npm install @openapitools/openapi-generator-cli -g
# Homebrew
brew install openapi-generator
# Docker
docker pull openapitools/openapi-generator-cli
Generate a Typed Client
# TypeScript (Axios)
openapi-generator-cli generate \
-i https://specs.apideck.com/crm.yml \
-g typescript-axios \
-o ./generated/crm-client \
--additional-properties=npmName=apideck-crm,supportsES6=true,withInterfaces=true
# Python (urllib3)
openapi-generator-cli generate \
-i https://specs.apideck.com/accounting.yml \
-g python \
-o ./generated/accounting-client \
--additional-properties=packageName=apideck_accounting
# Rust
openapi-generator-cli generate \
-i https://specs.apideck.com/crm.yml \
-g rust \
-o ./generated/crm-client \
--additional-properties=packageName=apideck_crm
# Swift
openapi-generator-cli generate \
-i https://specs.apideck.com/hris.yml \
-g swift5 \
-o ./generated/hris-client \
--additional-properties=projectName=ApideckHRIS
# Kotlin
openapi-generator-cli generate \
-i https://specs.apideck.com/crm.yml \
-g kotlin \
-o ./generated/crm-client \
--additional-properties=groupId=com.apideck,artifactId=crm-client
# Dart
openapi-generator-cli generate \
-i https://specs.apideck.com/crm.yml \
-g dart \
-o ./generated/crm-client
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.
- 2d ago First seen · 259 lines · 68 tokens per session scan A 9772f800b5b4
apideck-codegen is a skill published in the GitHub repository apideck-libraries/api-skills (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,072 once invoked, about $0.0003 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-31.
Other skills, from other repositories
component-family-consistency
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…
extract-design
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…
modular-scale-typography
Typography feels cohesive and intentional when font sizes follow a modular scale — a ratio-based sequence where every size is mathematically related to the others. Use when defining type scales, setting up design tokens, reviewing font size choices, or when typography feels inconsistent or arbitrary.
information-architecture
In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities…
algorithmic-color-palette
Derive a full UI colour palette algorithmically from one or two brand colours. Darker and lighter variants for interactive states, desaturated greys from the brand hue for borders and backgrounds, and semantic colours that feel coherent with the brand rather than generic. Use when building a colour system from scratch…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…