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 favcrm/mcp --skill favcrm-comms-approvalgit clone --depth 1 https://github.com/favcrm/mcpWrote 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/favcrm/mcp/favcrm-comms-approval)<a href="https://agentmods.dev/skills/favcrm/mcp/favcrm-comms-approval"><img src="https://agentmods.dev/badge/skills/favcrm/mcp/favcrm-comms-approval/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/favcrm/mcp/favcrm-comms-approval"><img src="https://agentmods.dev/badge/skills/favcrm/mcp/favcrm-comms-approval.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.00037 | $0.00309 |
| Opus 5.5 | $0.00015 | $0.00124 |
| Sonnet 5.5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
favcrm-comms-approval 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
FavCRM Comms Approval
Use this skill for marketing campaigns, customer reactivation, win-back messages, promotions, inbox replies, WhatsApp, SMS, email, broadcasts, campaign drafts, campaign validation, reminders, and any customer-facing message.
Operating Rules
- Never send customer-facing messages directly.
- Always use
request_send_approvalfor sends, broadcasts, campaigns, reminders, or replies that leave FavCRM. - Before approval, show recipient/channel/count, draft content, and reason.
- For bulk sends, show count, a 3-row recipient preview, the base audience, and confirmed exclusions before requesting approval.
- Match the merchant's language and tone. Use Traditional Chinese for zh-HK context.
Standard Flow
- Ground the recipient, conversation, campaign, or segment. Use
search_membersfor customer account IDs andlist_campaignsfor previous campaign IDs; never infer IDs from names. - Draft the message.
- For campaigns, set and read back
audienceExclusions, then callvalidate_campaignimmediately before approval. - Request merchant approval with the exact action type, payload, draft, recipients, and summary.
- Do not claim delivery until FavCRM reports completion.
Read references/comms-safety.md for approval payload patterns.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 31a82711614b
- 1mo ago First seen · 27 lines · 37 tokens per session scan A c258fde92ed1
favcrm-comms-approval is a skill published in the GitHub repository favcrm/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 309 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-08-31.
Other skills, from other repositories
kami
Generate PDFs, resumes, CVs, letters, slide decks, portfolios, one-pagers, white papers, and professional documents. Use when user asks to create a PDF, make a resume, write a letter, design slides, format a document, typeset a report, build a portfolio, make a presentation, or create a one-pager. Warm parchment…
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
kagen
Convert Kami HTML templates to production-grade PDF via Chromium/Playwright. Complements Kami (design) with PDF rendering. Use when user asks to generate PDF files, render HTML to PDF, or export documents.
motion-craft
Design GPU-accelerated animations with Web Animations API (WAAPI), Scroll-Driven Animations (ScrollTimeline/ViewTimeline), FLIP technique, easing systems, and accessibility (prefers-reduced-motion). Use when user asks to create animations, transitions, scroll effects, page transitions, or interactive motion for web…
Aesthetic Web Design
Apply professional, premium UI/UX design standards when building or styling web interfaces. Use this skill when the user asks to create a website, landing page, web app, dashboard, UI component, or any visual interface — or when they ask to make something look better, more professional, or more beautiful. Covers…
comprehensive-review
Comprehensive code review using parallel specialized subagents. If a PR URL is provided, fetches PR details and can post comments. If no PR is provided, reviews the diff between the current branch and its base branch plus any uncommitted changes. CRITICAL: this skill is costly, don't use it unless user explicitly…