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 acertagit 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/acerta)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/acerta"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/acerta/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/acerta"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/acerta.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.00069 | $0.01911 |
| Opus 5.5 | $0.00028 | $0.00764 |
| Sonnet 5.5 | $0.00014 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
acerta 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 'https://unify.apideck.com/connector/connectors/acerta' \ Copies of this mod
8 near-identical copies found in the catalogue:
- silae-fr — 91% identical, 69 lines differ
- jumpcloud — 89% identical, 81 lines differ
- liantis — 89% identical, 77 lines differ
- kenjo — 86% identical, 74 lines differ
- paylocity — 86% identical, 82 lines differ
- homerun-hr — 86% identical, 72 lines differ
- justworks — 86% identical, 83 lines differ
- cegid-talentsoft — 86% identical, 76 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acerta (via Apideck)
Access Acerta through Apideck's HRIS unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Acerta plumbing.
Beta connector. Acerta is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
acerta - Unified API: HRIS
- Auth type: oauth2
- Status: beta
- Gotchas: page
- Acerta docs: https://www.acerta.be
- Homepage: https://www.acerta.be/nl
At a glance
- Implementation difficulty: moderate — Credentials Issued by Acerta Per Employer
- Vendor partnership required: no (developer portal) — Contacting Acerta's integrations team opens API access, with advice on architecture and integration.
- Apideck-managed credentials: not available — Acerta issues credentials per employer and does not allow them to be shared.
- Account type required: An Acerta employer account; the Employer ID identifies which employer's agreements are listed.
- Consumer access level: No user sign-in: the connection runs on the credentials Acerta issues, not on a user role.
- Sandbox: available — An Acceptance environment; the Client ID is shared across environments and Acerta issues a separate secret for Acceptance.
- Authentication: Client credentials flow; no user-consent step.
- Webhooks: No webhooks - data is read by polling.
Important to know:
- Acerta publishes no self-service signup, so each consumer must request API access from Acerta before a connection can be tested.
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/acerta(overviewfield) is the live, authoritative version.
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 Changed · +20 lines a48f7bc54e00
- 1mo ago First seen · 132 lines · 69 tokens per session scan A 391e519ffe0a
acerta is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,911 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
inngest-realtime
Use when streaming durable workflow updates to a UI in real time — live order status pages that animate as steps complete, AI agent token streaming from a function to the browser, log tailing for long-running jobs, or human-in-the-loop approval flows that publish a prompt and wait for a user reply. Covers Inngest v4…
inngest-durable-functions
Use when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure failures — e.g., webhook handlers that drop events, flaky cron jobs, background jobs that fail mid-execution, or workflows that need to resume where…
inngest-brownfield-audit
Use when analyzing an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest. Covers repository discovery, framework and package detection, finding durability gaps in HTTP handlers, webhooks, cron jobs, queues, long-running jobs, AI agents, Agent Evals, polling loops, eval loops, and…
inngest-events
Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema…
inngest-middleware
Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly…
inngest-setup
Use when adding durable execution to a TypeScript project — building retry-safe webhook handlers, background jobs that survive crashes, scheduled tasks, or long-running workflows that outlive a single request. Covers Inngest SDK installation, client config, environment variables, serve endpoints (Next.js, Express…