What is contact-device-compliance?

A guarded workflow for inspecting one iBluSend contact or device, or changing one opt-out state or bot setting after confirmation.

It is for checking contact or device information and managing one messaging opt-out or bot-status setting in a connected workspace.

It limits sensitive account changes to one selected target and requires checking the current state before a change.

contact-device-compliance — Skill for Claude Code by ZachPulse

Install

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.

Any agent

npx skills add ZachPulse/iblusend-plugins --skill contact-device-compliance

Clone the repo

git clone --depth 1 https://github.com/ZachPulse/iblusend-plugins

Made for: Claude Code.

Or install iblusend, the plugin that ships this one along with the rest of its 3 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zachpulse/iblusend-plugins/contact-device-compliance/github.svg)](https://agentmods.dev/skills/zachpulse/iblusend-plugins/contact-device-compliance)

Your own site

<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.

Your own site · 80×15

<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>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 736 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00011	$0.00294
Sonnet 5.5	$0.00005	$0.00147
Haiku 4.5	$0.00003	$0.00074

Measured 2mo ago against content hash 74adf93ffd0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

plugins/iblusend/skills/contact-device-compliance/SKILL.md · 73 lines

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_out or set_bot_status for 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_contacts finds an existing record.
list_devices reports lines and current capacity/state for the consented workspace.
get_opt_out_status reads one contact's messaging consent state.
opt_out applies one opt-out or explicitly confirmed re-subscribe action.
get_bot_status reads current automation state.
set_bot_status changes one bot setting.

Read the full file on GitHub · 73 lines

Changes

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.

2mo ago First seen · 73 lines · 27 tokens per session scan A 74adf93ffd0b

Subscribe to this mod's changes

contact-device-compliance is a skill published in the GitHub repository ZachPulse/iblusend-plugins (0 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 736 once invoked, about $0.0001 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-08-31.

contact-device-compliance next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
contact-device-complianceZachPulse/iblusend-plugins	Skill	0	1mo ago	MIT	A	27	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code