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 m3taz-ahmed/ai-globals --skill marketing-automationgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/marketing-automation)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/marketing-automation"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/marketing-automation/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/m3taz-ahmed/ai-globals/marketing-automation"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/marketing-automation.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.00032 | $0.00596 |
| Opus 5.5 | $0.00013 | $0.00238 |
| Sonnet 5.5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
marketing-automation 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 1mo 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.
What it actually says
[SKILL] marketing-automation [OBJ] Design and deploy automated customer journeys — trigger → condition → action — that nurture leads, onboard users, and recover churn without manual effort.
[RULES]
- [REQ] Journey anatomy: Trigger (event) → Enrich → Condition (branch) → Action (message/task) → Wait → Loop/Exit. Model every flow as a state graph.
- [CMD] Context7 IDs:
n8n-io/n8n(node/trigger graph),automatisch/automatisch(Zapier alt, AGPL),knadh/listmonk(lists/campaigns),mautic/mautic(CampaignBundle state machine). - [REQ] Free-first engines: n8n (fair-code, self-host, internal use) or Automatisch (AGPL, self-host) default; Mautic for email journeys; Zapier/Make only as paid parity.
- [REQ] Drip design: welcome (3-5 emails), nurture (value→proof→offer), abandoned-cart, re-engagement. Each email uses
copy-frameworks(PAS/BAB). - [REQ] Idempotency + exits: every journey has an unsubscribe/opt-out path and a "do not contact" flag checked at each step (see
marketing-compliance). - [REQ] Lifecycle stages: subscriber → lead → MQL → SQL → customer → advocate. Map which journey owns each transition.
- [REQ] Error handling: failed step → retry + alert; dead-letter to human queue; never silently drop a customer.
- [REQ] Arabic/RTL: Arabic-language journeys with RTL templates; respect local sending-time windows; mirror logic for ar/en audiences.
- [REQ] Measurement: track open/click/convert per step; optimize the weakest node. Feed to
marketing-analytics. - [REQ] Approval gate: any journey that sends messages requires explicit user approval before activation (kernel write-gate).
[PROHIBIT]
- No automation that sends without an opt-out path.
- No journey activated without user approval.
- No infinite/non-terminating loops.
- No logging of PII/payment data.
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.
- 1mo ago First seen · 39 lines · 32 tokens per session scan A 5fa33708d748
marketing-automation is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 596 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.