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 S3YED/appie-kit --skill crm-reactivation-campaignsgit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/s3yed/appie-kit/crm-reactivation-campaigns)<a href="https://agentmods.dev/skills/s3yed/appie-kit/crm-reactivation-campaigns"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/crm-reactivation-campaigns/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/s3yed/appie-kit/crm-reactivation-campaigns"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/crm-reactivation-campaigns.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.00069 | $0.01500 |
| Opus 5 | $0.00034 | $0.00750 |
| Sonnet 5 | $0.00014 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
crm-reactivation-campaigns 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Reactivation Campaigns
Use when a CRM has hundreds+ of stale leads (applied but never contacted, booked but no-showed, went cold after contact) that need a structured re-engagement campaign.
Key Principle: Piggyback Don't Invent
Never create a separate "re-engagement offer." Anchor the outreach to whatever promotion/giveaway the business is already running. The existing campaign IS the re-engagement hook. This avoids confusing the owner ("what re-engagement offer?") and keeps messaging consistent.
Workflow
1. Audit the pipeline
Query the CRM to understand:
- Total opportunities by stage
- Contact coverage (phone, email, both, neither) per stage
- Activity recency — how long since last contact
- Top sources
- Monetary value assigned
CRITICAL: Data integrity rule — never fabricate. Only report data you have actually observed (queried from CRM, read from a file, confirmed by the user). If you do not know a field (e.g. welcome message date for a lead in the "no reply" group), mark it as unknown / N/A — do not infer, estimate, or backfill from other records. A blank cell is always better than a wrong one. The user will notice incorrect data immediately and it erodes trust in the entire report. When in doubt, report "No data" or leave the cell empty.
How to structure a lead status report:
- Group leads by verified stage only (completed call / booked no call / no reply / out of funnel)
- For each lead, include: name, contact info, verified stage
- Only include dates/fields you have direct evidence for
- If a lead's status changed since your last report, note the change explicitly so the user can confirm
- Before sending, scan for: any fabricated dates, assumed call statuses, or guessed data. Remove those.
GHL API quirks (v2):
- Base:
services.leadconnectorhq.com(v1 atrest.gohighlevel.comis Cloudflare-blocked) - Required header:
Version: 2021-07-28 - Phone numbers arrive partially masked (
+447****1234) — GHL privacy feature, not a query error - Max 100 results per page on opportunities search
- Store token in
/tmp/fileand read back to avoid shell redaction of secrets in command output
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.
- 9d ago First seen · 113 lines · 69 tokens per session scan A dc151a8f3253
crm-reactivation-campaigns is a skill published in the GitHub repository S3YED/appie-kit (9 stars, last pushed 17d ago), licensed MIT. It adds 69 tokens to every session and 1,500 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
agents-md-protocol
Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
python-memory-safe-scripts
Memory-safe Python script patterns for long-running processes under systemd MemoryMax constraints. Covers allocator purge (mimalloc/glibc malloctrim), HTTP response lifecycle, DataFrame cleanup, thread-local connection reuse, and periodic GC cadence. Battle-tested through 5 OOM optimization cycles on production GPU…