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 write-an-articlegit 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/write-an-article)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/write-an-article"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/write-an-article/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/write-an-article"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/write-an-article.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.00074 | $0.01527 |
| Opus 5 | $0.00037 | $0.00763 |
| Sonnet 5 | $0.00015 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
write-an-article 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write an Article
One skill, every help-center writing ask. Branch on type.
When to use
- from-ticket - "turn this ticket into article" / "document this
resolution" / "answered same question 3x - write up." Called
implicitly from
flag-a-signal signal=repeat-questionwhen cluster hits ≥3, no matching article. - known-issue - "draft known-issue doc for {bug}" / "P1, put up
status page" / chained from
draft-a-playbook. - broadcast-shipped - "shipped X - tell customers who asked" / "send 'you asked, we shipped' note."
- refresh-stale - "refresh articles affected by this ship" / "audit docs - pricing changed" / monthly help-center routine.
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.
- Knowledge base (Notion / Google Docs / Help Scout / Intercom) - mirror the draft to your published KB. Required for
from-ticketandrefresh-staleif you want me to push the draft there. - Dev tracker (GitHub / Linear) - pull bug context for the
known-issuedoc. Required forknown-issue. - Inbox (Gmail) - source the resolved thread when it's not already in
conversations.json. Optional.
If you ask for a known-issue page and your tracker isn't connected I stop and ask you to connect it.
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.
- Help-center platform - Required. Why I need it: format and tone vary by destination. If missing I ask: "Where do your help articles live today - Notion, Intercom, a docs site, or nowhere yet?"
- Voice samples - Required. Why I need it: KB articles in the wrong voice get rewritten. 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?"
- KB tone profile - Optional. Why I need it: some teams want KB more formal than chat replies. If you don't have it I keep going with TBD and match your reply voice.
- What shipped - Required for
broadcast-shipped. Why I need it: I won't broadcast a vague "we shipped stuff." If missing I ask: "What did you ship - give me a title and one sentence on what's new?" - What changed - Required for
refresh-stale. Why I need it: I scan articles for refs to the changed thing. If missing I ask: "What changed - pricing, a feature name, a UI flow, something else?"
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 · 109 lines · 74 tokens per session scan A 9ba32895ab2d
write-an-article is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 1,527 once invoked, about $0.0004 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
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.
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
auto-tag
Automatically analyze and tag untagged Gorgias tickets based on content.
bug-report
Extract a structured bug report from a support ticket and create a Linear issue.
escalate
Escalate a support ticket to a Linear issue and notify the team on Slack.
merge-tickets
Find and flag duplicate or related Gorgias tickets that should be merged.