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 akiotanaka847/qaio-desktop --skill draft-a-lifecycle-messagegit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/draft-a-lifecycle-message)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/draft-a-lifecycle-message"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/draft-a-lifecycle-message/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/akiotanaka847/qaio-desktop/draft-a-lifecycle-message"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/draft-a-lifecycle-message.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.00092 | $0.01640 |
| Opus 5 | $0.00046 | $0.00820 |
| Sonnet 5 | $0.00018 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
draft-a-lifecycle-message 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 7d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft a Lifecycle Message
One skill, every customer-lifecycle outreach your success motion need. Branches on type.
When to use
- welcome-series - "draft onboarding for {segment}" / "welcome series for new signups" / "activation drip."
- renewal - "renewal coming for {account}" / "draft 30/60/90 for {account}" / "pre-renewal outreach."
- expansion-nudge - "they ready for {tier}" / "draft expansion nudge for {account}" / "ceiling signal for {account}."
- churn-save - "save {account}" / "draft save for {customer}" / "they asked to cancel."
Connections I need
I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Email sender (Loops / Customer.io / Mailchimp) - format the welcome series for whichever lifecycle tool you actually send from. Required for
welcome-series. - CRM (HubSpot / Attio) - pull account record, owner, plan history for personalization. Required for
renewal/expansion-nudge/churn-save. - Billing (Stripe) - read monthly revenue, plan, renewal date so I can ground the ask in real numbers. Required for
renewal/expansion-nudge.
If none of the required categories are connected I stop and ask you to connect your CRM first.
Information I need
I read your support context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- Voice samples - Required. Why I need it: lifecycle copy in the wrong voice gets ignored. If missing I ask: "Want me to mine your sent folder for tone, or can you drop 3 to 5 of your recent customer emails?"
- Plan tiers + pricing - Required. Why I need it: knowing what "upgrade" or "downgrade" means for this account. If missing I ask: "What plans do you sell and roughly what do they cost?"
- Renewal cadence - Required for
renewal. Why I need it: 30/60/90 sequence keys to your renewal window. If missing I ask: "Are renewals annual, monthly, or something else - and when does this account's clock end?" - Approved save offers - Required for
churn-save. Why I need it: I won't invent a discount or credit. If missing I ask: "When someone tries to cancel, what can you actually offer them - pause, downgrade, refund, concierge time?" - Activation milestones - Required for
welcome-series. Why I need it: each touch needs a real "aha" event to push toward. If missing I ask: "What's the first thing a new signup needs to do for the product to click - and what comes next?"
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.
- 7d ago First seen · 78 lines · 92 tokens per session scan A 7b6fb42322c0
draft-a-lifecycle-message is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 92 tokens to every session and 1,640 once invoked, about $0.0005 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-05.
Other skills, from other repositories
support-digest
A local tool that reads exported customer-support tickets in JSON or CSV and produces a daily summary after hiding personal information. It does not fetch data from support systems or call outside APIs.
sillytavern-shadow
A fast-response workflow for debugging and implementation. It moves from noticing a request or problem to providing support, solving it, and checking the work with investigation steps.
moonpay-feedback
Submit feedback, bug reports, or feature requests for the MoonPay CLI. Use when the user encounters issues, wants to suggest improvements, or has general feedback.
customer-support-expert
Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics. Use when the user mentions helpdesk or service desk, ticketing, SLA targets, knowledge bases, escalation workflows, CSAT/NPS, or customer success operations.
Troubleshooting Guide Builder
Builds a structured troubleshooting guide with symptom → cause → fix format for any tool or system.
supportive-conversation
Generate supportive responses with safety boundaries. Use when user asks to 'be supportive', 'help with emotional support', 'provide encouragement', 'respond with empathy', 'offer emotional support'.