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-comment-to-dm/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-comment-to-dm)<a href="https://agentmods.dev/skills/enriquemarq1/zernio-library-skills/zernio-comment-to-dm"><img src="https://agentmods.dev/badge/skills/enriquemarq1/zernio-library-skills/zernio-comment-to-dm/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-comment-to-dm"><img src="https://agentmods.dev/badge/skills/enriquemarq1/zernio-library-skills/zernio-comment-to-dm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 58 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 39 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00131 | $0.01131 |
| Opus 5 | $0.00066 | $0.00566 |
| Sonnet 5 | $0.00026 | $0.00226 |
| Haiku 4.5 | $0.00013 | $0.00113 |
Grade A, and why
zernio-comment-to-dm 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 12d 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.
> the recipe. Claude executes with `curl` (or the user's HTTP tool). Always confirm with the How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zernio-comment-to-dm
Turn a comment section into captured leads. When someone comments your keyword on a post, Zernio auto-DMs them — and this skill lets you set that up just by asking Claude, for any post or keyword, in seconds. No dashboard clicking, no cloning workflows.
The skill informs; the agent acts. This file gives Claude the Zernio API contract + the recipe. Claude executes with
curl(or the user's HTTP tool). Always confirm with the user before creating/activating an automation (it goes live on a real audience).
What you can ask
- "When someone comments GUIDE on my latest post, DM them my free template link."
- "New automation: post
<id>, keyword PRICING, DM the pricing + ask if they want a call." - "Pause / update / delete the GUIDE automation."
- "Walk a short sequence: DM them the resource, then if they reply, ask for their email."
What Claude needs (ask the user once, then remember in-session)
- ZERNIO_API_KEY —
Authorization: Bearer <key>(zernio.com → Settings → API keys). - profileId + accountId — the Zernio profile + connected IG/FB account
(
GET /profiles,GET /accountsif unknown). - platformPostId — the post the automation watches (the IG/FB post ID).
- keyword(s), the DM message, optional public comment reply.
The recipe (Claude follows this)
1. Create the comment automation (the core — native, one call)
curl -s -X POST "https://zernio.com/api/v1/automations" \
-H "Authorization: Bearer $ZERNIO_API_KEY" -H "Content-Type: application/json" \
-d '{
"profileId": "<profileId>",
"accountId": "<accountId>",
"platformPostId": "<platformPostId>",
"name": "GUIDE — free template",
"keywords": "GUIDE",
"dmMessage": "Hey! Here is the free template you asked for 👇 [link]. Want me to walk you through it?",
"commentReply": "Check your DMs 📩",
"isActive": true
}'
Returns the automation id. From now on, every comment matching the keyword auto-DMs.
What ships with it
2 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.
- 12d ago First seen · 79 lines · 131 tokens per session scan A fa4eca68fb6a
zernio-comment-to-dm is a skill published in the GitHub repository Enriquemarq1/zernio-library-skills (39 stars, last pushed 23d ago), licensed MIT. It adds 131 tokens to every session and 1,131 once invoked, about $0.0007 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…