Borrowing it
Nothing to install: this file belongs to Enriquemarq1/zernio-library-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Enriquemarq1/zernio-library-skills/main/.claude/skills/zernio-inbox-integration/SKILL.mdgit clone --depth 1 https://github.com/Enriquemarq1/zernio-library-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/enriquemarq1/zernio-library-skills/zernio-inbox-integration)<a href="https://agentmods.dev/skills/enriquemarq1/zernio-library-skills/zernio-inbox-integration"><img src="https://agentmods.dev/badge/skills/enriquemarq1/zernio-library-skills/zernio-inbox-integration/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/enriquemarq1/zernio-library-skills/zernio-inbox-integration"><img src="https://agentmods.dev/badge/skills/enriquemarq1/zernio-library-skills/zernio-inbox-integration.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.00055 | $0.01107 |
| Opus 5.5 | $0.00022 | $0.00443 |
| Sonnet 5.5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
zernio-inbox-integration 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 21d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zernio inbox integration
This is a standalone integration skill, not a stage of the white-label blueprint. It works with existing apps regardless of how they were built. Its instructions and official-documentation links are self-contained; the library relationship below is optional compatibility context.
Use Map → Connect → Integrate → Verify to add Zernio's messaging capabilities to the user's own application. The app already exists by default. This is an implementation framework, not a software package or a guarantee of instant channel activation. Follow the agent brief and prompt sequence.
Start from official documentation, not Enrique's legacy Zernio skills. Adapt to the application's existing framework, authentication, data model and design. Do not scaffold a new app or replace its stack unless requested. If no repository is available, produce an integration plan and ask for the target app before making architectural commitments.
Use the API contracts and integration pitfalls while implementing; it records the documentation audit and points to the exact sources. Use the Claude Code testing handoff for a realistic end-to-end evaluation. Neither reference substitutes for live verification.
Guide the user through the process: identify the next action, implement everything possible autonomously, and ask only for account-owner actions the agent cannot perform, such as completing consent. Explain where to click and how readiness will be checked. Keep an integration progress record in the target project with stage, completed evidence, blocked prerequisites and next action. Never label a stage complete just because its code exists.
Relationship to Enrique's library
The white-label-blueprint already covers creating a branded social app: account connection, client workspaces, publishing and account-health webhooks. Its stage 7 already sketches an inbox tab with history, replies, read state and comments. This skill develops that messaging integration in depth and can also operate on any existing app; the blueprint is not a required dependency. Reuse existing connections, profile mappings, routes and components instead of rebuilding them. Verify current API contracts and authorization requirements independently; the starter's unlisted client links and UI profile filters are not production access control. See library relationship when integrating into a blueprint-derived app.
What ships with it
5 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.
- 21d ago First seen · 43 lines · 55 tokens per session scan A 527e604c4b92
zernio-inbox-integration is a skill published in the GitHub repository Enriquemarq1/zernio-library-skills (49 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 1,107 once invoked, about $0.0002 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-10-08.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.