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 ZachPulse/iblusend-plugins --skill contact-device-compliancegit clone --depth 1 https://github.com/ZachPulse/iblusend-pluginsWrote 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/zachpulse/iblusend-plugins/contact-device-compliance)<a href="https://agentmods.dev/skills/zachpulse/iblusend-plugins/contact-device-compliance"><img src="https://agentmods.dev/badge/skills/zachpulse/iblusend-plugins/contact-device-compliance/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/zachpulse/iblusend-plugins/contact-device-compliance"><img src="https://agentmods.dev/badge/skills/zachpulse/iblusend-plugins/contact-device-compliance.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.00027 | $0.00736 |
| Opus 5 | $0.00014 | $0.00368 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
contact-device-compliance 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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contact, device, and compliance operations
Use this workflow for a focused operational check or one narrowly scoped change in the connected workspace.
Guardrails
- Work on exactly one workspace and one contact or one automation setting per change.
- Start read-only. Resolve the target and show current state before proposing a mutation.
- Contact creation and profile-field updates are not available in this public workflow. Never invent a hidden write path, bulk importer, or customer-data export.
- Never treat a phone number as belonging to a person unless the connected workspace data supports that association.
- Device state is a reported snapshot. Offline/online does not guarantee that a future message will fail/succeed.
Stop and cancellation control
- The newest user instruction is authoritative. If, before a write tool starts, the user says stop, cancel, hold, pause, do not send, changes the request, or otherwise withdraws approval, cancel the pending action immediately.
- Cancellation invalidates every earlier preview and confirmation.
- Do not call
opt_outorset_bot_statusfor the cancelled action, even if an earlier message approved it. - If the provider or host rejects or closes its confirmation, treat that as cancellation too.
- Silence, elapsed time, or approval for a different payload never restores authorization.
- To resume or act on a changed request, rebuild the exact preview from current state and obtain fresh explicit confirmation in a later user turn.
- After a pre-call cancellation, acknowledge that no write ran and stop this workflow unless the newest instruction explicitly replaces it with read-only work.
- If a write tool may already have started, do not claim that it was cancelled. Check status or current state, report the facts, and never retry the write automatically.
Tool selection
list_contactsfinds an existing record.list_devicesreports lines and current capacity/state for the consented workspace.get_opt_out_statusreads one contact's messaging consent state.opt_outapplies one opt-out or explicitly confirmed re-subscribe action.get_bot_statusreads current automation state.set_bot_statuschanges one bot setting.
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.
- 9d ago First seen · 73 lines · 27 tokens per session scan A 74adf93ffd0b
contact-device-compliance is a skill published in the GitHub repository ZachPulse/iblusend-plugins (0 stars, last pushed 16d ago), licensed MIT. It adds 27 tokens to every session and 736 once invoked, about $0.0001 per session on Opus 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…