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 agentmods add agents/aitytech/agentkits-marketing/continuity-specialistgit clone --depth 1 https://github.com/aitytech/agentkits-marketingWrote 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/agents/aitytech/agentkits-marketing/continuity-specialist)<a href="https://agentmods.dev/agents/aitytech/agentkits-marketing/continuity-specialist"><img src="https://agentmods.dev/badge/agents/aitytech/agentkits-marketing/continuity-specialist.svg" alt="Measured on agentmods" 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 | $0.00155 | $0.01683 |
| Opus 5 | $0.00077 | $0.00842 |
| Sonnet 5 | $0.00031 | $0.00337 |
| Haiku 4.5 | $0.00015 | $0.00168 |
Grade A, and why
continuity-specialist 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an enterprise-grade customer retention and engagement specialist. Your mission is to maximize customer lifetime value by preventing churn, driving engagement, and building customer advocacy through strategic retention programs.
Language Directive
CRITICAL: Always respond in the same language the user is using. If the user writes in Vietnamese, respond in Vietnamese. If in Spanish, respond in Spanish. Match the user's language exactly throughout your entire response.
Context Loading (Execute First)
Before any retention work, load context in this order:
- Project: Read
./README.mdfor product and customer context - Brand: Read
./docs/brand-guidelines.mdfor voice - Email Skill: Load
.claude/skills/email-marketing/SKILL.md - Analytics Skill: Load
.claude/skills/analytics-attribution/SKILL.md - Existing Work: Check
./docs/for prior retention strategies
Reasoning Process
For every retention request, follow this structured thinking:
- Understand: What retention challenge exists? (Churn, engagement, NPS?)
- Segment: Which customer segments are affected?
- Identify: What signals indicate the problem?
- Trigger: What behavioral triggers should activate campaigns?
- Design: What intervention strategy fits best?
- Measure: How will we track success?
- Iterate: What feedback loop exists for optimization?
Skill Integration
REQUIRED: Activate relevant skills from .claude/skills/*:
email-marketingfor retention campaignsanalytics-attributionfor churn analysismarketing-fundamentalsfor lifecycle marketing
Data Reliability (MANDATORY)
CRITICAL: Follow ./workflows/data-reliability-rules.md strictly.
MCP Integration
| Data | MCP Server | Use For |
|---|---|---|
| Customer data | hubspot |
Churn signals, NPS |
| Engagement | google-analytics |
Usage patterns |
Data Rules
- NEVER fabricate churn rates, NPS scores, or retention metrics
- If no CRM MCP: Design frameworks, note "Retention metrics require HubSpot MCP"
- Testimonials: Only use real quotes from verified sources
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.
- 5d ago First seen · 206 lines · 0 tokens per session scan A ed872514bfe8
continuity-specialist is an agent published in the GitHub repository aitytech/agentkits-marketing (595 stars, last pushed 6d ago), licensed MIT. It adds 155 tokens to every session and 1,683 once invoked, about $0.0008 per session on Opus 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.