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 namelygit 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/namely)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/namely"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/namely/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/namely"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/namely.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.01869 |
| Opus 5.5 | $0.00028 | $0.00748 |
| Sonnet 5.5 | $0.00014 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
namely 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 15d 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/namely' \ This is a copy
81% identical to acerta — 77 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Namely (via Apideck)
Access Namely 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 Namely plumbing.
Quick facts
- Apideck serviceId:
namely - Unified API: HRIS
- Auth type: oauth2
- Gotchas: page
- Namely docs: https://developers.namely.com
- Homepage: https://www.namely.com/
At a glance
- Implementation difficulty: moderate — Partner Enquiry or Admin Access Needed for OAuth Credentials
- Vendor partnership required: no (developer portal) — Namely's partner page takes integration enquiries at [email protected].
- Apideck-managed credentials: not available — Apideck holds no Namely OAuth app.
- Account type required: Paid Namely account with API access enabled.
- Consumer access level: A Namely administrator, or a user an administrator has granted API access.
- Sandbox: not available — Test against a live Namely account; Namely documents no public route to request a sandbox tenant.
- Rate limits: 100 requests per minute on GET /profiles.
- Authentication: Authorization Code flow.
- Webhooks: Virtual webhooks - employee created, updated and terminated events.
Important to know:
- You connect Namely with your own OAuth client ID and secret. Sources disagree on whether a tenant admin can create these directly or they come through Namely's partner route, so confirm the route with Namely before you plan around it.
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/namely(overviewfield) is the live, authoritative version.
When to use this skill
Activate this skill when the user explicitly wants to work with Namely — for example, "sync employees in Namely" or "list time-off requests in Namely". This skill teaches the agent:
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.
- 15d ago Changed · +21 lines 11e76c0b12a5
- 1mo ago First seen · 128 lines · 69 tokens per session scan A 0b23fb39c88f
namely is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 1,869 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 81% identical to acerta, differing in 77 lines, and is treated as a copy.
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-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-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…
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-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…