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.
git clone --depth 1 https://github.com/indranilbanerjee/neels-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/commands/indranilbanerjee/neels-plugins/engagement)<a href="https://agentmods.dev/commands/indranilbanerjee/neels-plugins/engagement"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/neels-plugins/engagement/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/commands/indranilbanerjee/neels-plugins/engagement"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/neels-plugins/engagement.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.02409 |
| Opus 5.5 | $0.00011 | $0.00964 |
| Sonnet 5.5 | $0.00005 | $0.00482 |
| Haiku 4.5 | $0.00003 | $0.00241 |
Grade A, and why
engagement 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 4d 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.
This is a copy
97% identical to engagement — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:engagement — 12-Part Engagement Workflow
The engagement command family runs a complete marketing engagement using the 12-Part methodology. Every brand engagement runs through 12 parts in sequence, producing a canonical set of files at each stage.
This command is the entry point. It invokes the engagement-workflow skill, which delegates to part-specific skills (four-core-documents, client-validation-document, growth-plan, yearly-planner, continuous-improvement-loop).
Subcommands
/digital-marketing-pro:engagement start <brand-slug> <engagement-id>
Initialise a new engagement. Creates the directory tree, writes _engagement.json, walks the user through Part 1 Stone vs Opinion intake.
Example:
/digital-marketing-pro:engagement start acme-corp 2026-q2
Pre-condition: Brand profile must exist at ~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run /digital-marketing-pro:brand-setup first.
Checkpointing & resume: The full checkpoint protocol — open a run on start, save each part as it completes, run /digital-marketing-pro:check --full before the Part 5 and Part 8 deliverables, then publish and finalize at the end — lives in the skill. See engagement-workflow/SKILL.md § Checkpointing & Resume (the single source of truth). Each part's checkpoint saves that part's own deliverable path (Part 3 saves the Four Core Documents, Part 8 saves the Growth Plan — never a placeholder for a different part). An interrupted run resumes with /digital-marketing-pro:resume, and the finished files land in the visible output folder (/digital-marketing-pro:output-folder {brand}).
/digital-marketing-pro:engagement status [brand-slug] [engagement-id]
Show the current engagement status. If brand and id are omitted, shows all active engagements.
Example:
/digital-marketing-pro:engagement status acme-corp 2026-q2
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.
- 4d ago First seen · 178 lines · 27 tokens per session scan A 97c6f4e62cb5
engagement is a command published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 2,409 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to engagement, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
create-content
Generate SEO + AEO + GEO-optimized content for a topic or keyword.
diagnose-underperformer
Diagnose why a specific Google Ads or Meta Ads campaign / ad set / ad is underperforming and prescribe the next concrete action. Use when the user says something like "why is X not converting?", "this campaign is wasting money", or "why are impressions so low?". Read-only — no changes are made.
launch-pmax
Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.
create-content
Create a full content piece through the 10-phase pipeline. "create content about X".
social-adapt
Repurpose an article into social posts for 8 platforms. "make social posts from this blog".
ma-strategy
Develop M&A strategy including target screening, synergy analysis, or integration planning.