Describe the campaign. Your agent handles the workflow.

Paste this into the agent you already use. It can install the public, version-pinned integration and guide the campaign workflow without learning DM Faster's screens or internal tool names. Account access still requires your approval in a focused browser page.

Set up DM Faster Agent 1.0 for this agent.

1. Confirm Node.js 24 is available.
2. Prefer the portable DM Faster Agent Plugins package when this host supports it. If this is Codex, add the dmfaster/agents marketplace and install dmfaster@dmfaster-agents. If this is Claude Code, install the reviewed bundle from the same repository. Otherwise configure the version-pinned @dmfaster/mcp-server@1.4.0 command for this MCP host.
3. Run the version-pinned DM Faster CLI browser login. Let me compare and approve the confirmation code in the focused DM Faster page myself.
4. Verify authentication and run one workspace briefing.
5. When I describe a campaign goal, carry it through grounded industry lookup, complete-plan validation, exact audience preview, and an idempotent private disabled draft. Keep the complete latest campaign state on every planning call.
6. For company research, discover filters, search companies, inspect their full profiles, and save a private company list only when requested. Preserve real contact routes; never treat a generated company identity as an Instagram handle.
7. When I explicitly say to launch or pause, run the matching preflight. If my connection has owner-granted campaigns:control and preflight returns ready, execute with the returned authorization immediately. Show a browser approval or setup handoff only when DM Faster requires it.
8. Use delivery inspection and update to change a running campaign’s cap, pace, or automatic sending window. Inspect operation receipts and sending health before claiming a launch succeeded or messages were sent.

Never ask me to paste a DM Faster token, browser cookie, or extension credential into chat. Do not silently install a browser extension, guess an audience total, send replies, book meetings, or bypass DM Faster's approval boundary.

1. 01Installs the signed 1.4.0 integration
2. 02Opens focused browser authentication
3. 03Plans from a complete stateless campaign brief
4. 04Launches only when you explicitly instruct it

The Codex plugin bundles the DM Faster skill and local MCP server configuration. Add the public repository marketplace, install the plugin, then start a new Codex session so its skills and tools load.

Review the official public source on GitHub before installing.

codex plugin marketplace add dmfaster/agents
codex plugin add dmfaster@dmfaster-agents

Claude Code can install the same reviewed bundle from the same public repository. A Claude subscription is not required to use DM Faster through Codex or a generic MCP host.

claude plugin marketplace add dmfaster/agents
claude plugin install dmfaster@dmfaster-agents

Prefer the plugin when your host supports it. For Hermes, another MCP host, or a shell-only workflow, use the pinned MCP or CLI commands below instead of cloning DM Faster's private product repository.

The public DM Faster plugin includes the portable Agent Plugins files that describe the skill and MCP connection together. Compatible clients discover the root plugin.json, the skills/ directory, and the schema-backed mcp.json; Codex, Claude Code, and Cursor manifests remain alongside them for host-specific installation.

dmfaster/
├── plugin.json
├── mcp.json
└── skills/
    └── dmfaster/
        └── SKILL.md

Agent Plugins standardizes package discovery, not a universal installer or authentication flow. Install through your host's supported repository or plugin flow, then authenticate with the pinned CLI. Never put a DM Faster token, browser cookie, or extension credential in mcp.json.

Run the public CLI without a global install. Login prints a short confirmation code and opens an app.dmfaster.com/connect/agent/… page.

npx --yes @dmfaster/cli@1.4.0 auth login --json

Compare both codes before approving. Review the requesting client, workspace, expiry, and exact scopes. The default full profile enables the complete Agent 1.0 flow; append --access read, plan, or draft for a smaller ceiling.

npx --yes @dmfaster/cli@1.4.0 auth status --json
npx --yes @dmfaster/cli@1.4.0 workspace briefing --json

The CLI and MCP server share the operating-system credential. macOS uses Keychain; supported Linux desktops use Secret Service through secret-tool. Unsupported stores fail closed instead of writing a plaintext token. The focused browser page never receives or displays the issued credential.

1. 01

   Brief

   The agent reads workspace priorities and turns your goal into a complete versioned campaign state.

2. 02

   Ground

   Industry lookup resolves supported TOL industries and asks you when the target is ambiguous.

3. 03

   Validate

   DM Faster checks targeting, messages, channels, delivery settings, limits, and required setup.

4. 04

   Preview

   The agent receives an exact audience total. A sample, estimate, or lower bound never substitutes for it.

5. 05

   Prepare

   List and campaign preparation create only private, disabled, retry-safe drafts.

6. 06

   Check readiness

   Preflight checks the exact campaign version, connection permissions, and browser readiness. It returns authorization or the required approval or setup handoff.

7. 07

   Act

   After your explicit launch or pause instruction, the agent uses DM Faster's short-lived, single-use authorization. A delegated connection needs no extra approval click.

If browser sending is not ready, launch preflight keeps the campaign disabled and returns one setup link plus the exact resume call. The user installs or reconnects the extension through the browser store; websites and agents cannot install it silently.

Ask your agent to find companies using Shopify with active Meta ads. It first discovers the available Companies app filters, then searches with technology and ad-activity criteria together. It can inspect full company profiles, financials, technology evidence, social profiles, and decision-makers. Search supports every current Companies app filter; country-specific availability and data freshness still apply.

{
  "filters": {
    "technologies": ["shopify"],
    "metaAdsActiveOnly": true
  },
  "pageSize": 50
}

Save this JSON as company-search.json, then run the command below. Your agent can prepare the file for you. Use the returned query signature and revision when paging; a page size is not the total matching audience.

npx --yes @dmfaster/cli@1.4.0 companies search --input company-search.json --json

Saved company lists preserve available real email, LinkedIn, phone, Instagram, and Facebook contact routes. Decision-maker names and roles stay with their respective email, LinkedIn, or phone contact. Companies without contacts remain useful research rows; generated company identities are never Instagram targets. Saving a research list creates no campaign and sends nothing. Contact data is a stored snapshot, not proof of deliverability. Older lists are not automatically backfilled with contacts that were previously lost.

Your agent can inspect and update an ongoing Instagram campaign’s daily cap, pacing, and automatic sending window. It reads the current revision, applies your requested changes, and verifies the saved result. Pacing accepts 12–3,600 seconds. Daily caps are validated against the account’s current limit; provider limits still apply. Windows use the returned workspace timezone and can be toggled on or off.

Updating delivery settings does not launch a stopped campaign. A launch receipt or browser acknowledgement is not evidence that a message was delivered: the agent checks operation status and sending health before reporting success.

Authenticate once with the CLI, then configure the signed stdio server. The configuration below is the portable Agent Plugins mcp.json format: its schema and transport type tell compatible hosts exactly how to discover the server. It reads the same OS-stored credential, keeps MCP protocol messages on stdout, and sends diagnostics only to stderr.

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "dmfaster": {
      "type": "stdio",
      "command": "npx",
      "args": ["--yes", "@dmfaster/mcp-server@1.4.0"]
    }
  }
}

Restart the host if it cannot reload MCP configuration. Agent 1.0 requires MCP 2026-07-28 and intentionally does not downgrade to the 2025 protocol. Hosts that have not implemented that revision can use the version-pinned CLI with structured JSON instead.

The server is stateless: each planning call carries the complete latest campaign state. Durable campaign data, permissions, idempotency, exact counts, and approvals remain on DM Faster's server.

The CLI and local MCP server expose the same 31 domain tools. MCP also offers an optional campaign workspace editor. Company research, saved lists, campaign preparation, delivery controls, and reporting are available; full live-app parity is still in progress.

Lost a device or stopped using an agent? Open the private connected agents page to revoke its access immediately. That page lists and disconnects existing connections only; it cannot create credentials.

Agent 1.0 is public as signed, provenance-backed npm packages and a repository marketplace for Codex and Claude Code. The public plugin also includes the portable Agent Plugins package for compatible clients. The local CLI and stdio MCP server work on macOS and supported Linux desktops with Node.js 24.

There is no hosted remote MCP endpoint or Windows credential-store integration in this release. Each client still controls how it installs and lists Agent Plugins; Cursor installation requires its separate marketplace review. The local stdio release is not a universal ChatGPT/Codex directory listing; use the reviewed repository marketplace or version-pinned local commands shown here.