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 set-up-my-support-infogit 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/set-up-my-support-info)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/set-up-my-support-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-support-info/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/set-up-my-support-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-support-info.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.00072 | $0.01443 |
| Opus 5 | $0.00036 | $0.00722 |
| Sonnet 5 | $0.00014 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
set-up-my-support-info 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up My Support Info
Own context/support-context.md. Only skill that creates or updates full doc (routing section also editable by tune-my-routing). Every other skill read it before work - until exists, stop and ask you run me first.
When to use
- "set up our support context" / "define our support context" / "let's do the context doc".
- "update the context doc" / "a new tier / VIP / gotcha - fix the context".
- Called implicitly by any other skill needing context and finds doc missing - but only after confirming with you.
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.
- Docs / notes (Google Docs / Notion) - pull existing positioning or product docs to seed the draft. Optional.
- Billing (Stripe) - read live plan tiers if you'd rather I infer them than ask. Optional.
- Dev tracker (GitHub / Linear) - named target for the bug routing rule. Optional.
If none of these are connected I keep going - this skill is mostly an interview, connections only speed it up.
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.
- Company basics - Required. Why I need it: anchors the product overview at the top of the doc. If missing I ask: "What does the product do in one sentence, and who buys it?"
- Customer segments + VIP list - Required. Why I need it: VIPs get P1 priority regardless of content; segments shape every reply. If missing I ask: "Who are your top 5 customers right now, and are there segments (SMB / mid-market / enterprise) I should treat differently?"
- Response-time targets - Required. Why I need it: response-time expectations per tier. If missing I ask: "What response time do you want to hit for your most urgent tickets, and what's acceptable for the rest?"
- Routing categories - Required. Why I need it: triage and signal detection map every inbound message to one. If missing I ask: "When a ticket comes in, what buckets do you sort it into - bug, how-to, billing, anything else?"
- Escalation tiers - Required. Why I need it: P1 / P2 / P3 / P4 definitions for triage. If missing I ask: "What makes something a fire-drill versus a same-day versus a this-week thing?"
- Verbatim voice samples - Optional. Why I need it: tone section reads truer with real phrases. If you don't have it I keep going with TBD and recommend running voice calibration.
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 · 74 lines · 72 tokens per session scan A b33a7f65d0c2
set-up-my-support-info is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,443 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.