A plugin that connects an agent to iBluSend, a service for managing conversations, contacts, devices, iMessages, and SMS from one consented workspace.

It is for triaging conversations, inspecting contacts and devices, and sending iMessages or SMS with user confirmation.

It gives messaging tasks a defined workspace and includes guarded workflows for reading information and sending confirmed messages.

iblusend — Plugin 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.

Claude Code

/plugin marketplace add ZachPulse/iblusend-plugins

agentmods

npx agentmods add plugins/zachpulse/iblusend-plugins/iblusend

Clone the repo

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

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

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

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/.claude-plugin/plugin.json · 26 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "iblusend",
  "displayName": "iBluSend",
  "version": "1.0.0",
  "description": "Safely triage conversations, inspect contacts and devices, and send confirmed iMessages and SMS through one consented workspace.",
  "author": {
    "name": "iBluSend",
    "email": "[email protected]",
    "url": "https://iblusend.com"
  },
  "homepage": "https://iblusend.com/features/ai-assistants",
  "repository": "https://github.com/ZachPulse/iblusend-plugins",
  "license": "MIT",
  "keywords": [
    "imessage",
    "sms",
    "messaging",
    "contacts",
    "inbox",
    "crm"
  ],
  "skills": "./skills/",
  "mcpServers": "./.mcp.json"
}

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.

yesterday First seen · 26 lines scan A 3414e8a0f055

Subscribe to this mod's changes

iblusend is a plugin published in the GitHub repository ZachPulse/iblusend-plugins (0 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

iblusend

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc