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 apideck-libraries/api-skills --skill apideck-nodegit clone --depth 1 https://github.com/apideck-libraries/api-skillsWrote 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/apideck-libraries/api-skills/apideck-node)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/apideck-node"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/apideck-node/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/apideck-libraries/api-skills/apideck-node"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/apideck-node.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.00119 | $0.02499 |
| Opus 5.5 | $0.00048 | $0.01000 |
| Sonnet 5.5 | $0.00024 | $0.00500 |
| Haiku 4.5 | $0.00012 | $0.00250 |
Grade A, and why
apideck-node 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 1mo 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apideck TypeScript SDK Skill
Overview
The Apideck Unified API provides a single integration layer to connect with 200+ third-party services across accounting, CRM, HRIS, file storage, ATS, e-commerce, and more. The official TypeScript SDK (@apideck/unify) provides typed clients for all unified APIs.
Key capabilities:
- Accounting - Invoices, bills, payments, ledger accounts, journal entries, tax rates, balance sheets, P&L
- CRM - Contacts, companies, leads, opportunities, activities, pipelines, notes
- HRIS - Employees, departments, payrolls, time-off requests, schedules
- File Storage - Files, folders, drives, shared links, upload sessions
- ATS - Jobs, applicants, applications
- Vault - Connection management, OAuth flows, custom field mapping
- Vault JS - Embeddable modal UI for users to authorize connectors and manage settings
- Webhook - Event subscriptions and real-time notifications
Installation
npm add @apideck/unify
Requires Node.js 18+. The SDK is fully typed with TypeScript definitions.
IMPORTANT RULES
- ALWAYS use the
@apideck/unifySDK. DO NOT make rawfetch/axioscalls to the Apideck API. - ALWAYS pass
apiKey,appId, andconsumerIdwhen initializing the client. These are required for all API calls. - ALWAYS set the
APIDECK_API_KEYenvironment variable rather than hardcoding API keys. - USE
serviceIdto specify which downstream connector to use (e.g.,"salesforce","quickbooks","xero"). If a consumer has multiple connections for an API,serviceIdis required. - USE cursor-based pagination with
for await...offor iterating large result sets. DO NOT implement manual pagination. - USE the
filterparameter to narrow results server-side. DO NOT fetch all records and filter client-side. - USE the
fieldsparameter to request only the columns you need. This reduces response size and improves performance. - ALWAYS handle errors with try/catch. The SDK throws typed errors for different HTTP status codes.
- DO NOT store Apideck API keys, App IDs, or Consumer IDs in source code. Use environment variables or a secrets manager.
What ships with it
8 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.
- 1mo ago First seen · 277 lines · 119 tokens per session scan A 59199e9cc7e1
apideck-node is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 2,499 once invoked, about $0.0005 per session on Opus 5.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
502-frameworks-micronaut-rest
Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via…
workflow-skill-evals
Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…
go-testing
Use when writing, reviewing, or running Go tests in test.go files — writing tests for a Go package, adding table-driven tests with t.Run subtests, testing a Go HTTP handler with httptest, adding a Go fuzz test or seed corpus, running or choosing go test flags (-race, -fuzz, -fuzztime), or deciding whether to use…
python-testing
Python test authoring and review with pytest. Use when writing, adding, generating, or reviewing Python tests or unit tests for a function, module, or class; running pytest or a single test (the -k flag and other invocation flags for a Makefile or CI); parametrizing test cases into the table-driven pattern; setting up…
terraform-validate
Format and validate Terraform code with the fmt / init / validate / tflint loop. Use after editing any .tf file, before committing Terraform changes, when asked to lint, format, validate, or check Terraform modules and root configurations, or when setting up tflint for a repository.
api-testing
REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts.