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 mine-my-ticketsgit 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/mine-my-tickets)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/mine-my-tickets"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/mine-my-tickets/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/mine-my-tickets"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/mine-my-tickets.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.00064 | $0.01387 |
| Opus 5 | $0.00032 | $0.00694 |
| Sonnet 5 | $0.00013 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
mine-my-tickets 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mine My Tickets
Different from flag-a-signal signal=repeat-question. That skill outputs KB-gap candidates (operational view). This one outputs strategic voice-of-customer report (product/positioning view). Same source data, different consumer.
When to use
- "mine the last {N} tickets for themes."
- "what are customers asking for?"
- Before writing roadmap, landing-page update, or investor update.
- Ad hoc strategic-research requests.
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.
- Inbox (Gmail) - source of customer threads when
conversations.jsondoesn't cover the window. Optional if local data is current. - Support helpdesk (Intercom / Zendesk / Help Scout) - alternate ticket source. Optional.
If neither is connected and the local conversation index is thin I stop and ask you to link your inbox or helpdesk so I have enough signal.
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.
- Current positioning - Required. Why I need it: I flag friction by comparing real customer language against what you claim. If missing I ask: "How do you describe what the product does today - share your homepage URL or one paragraph?"
- Time window - Required. Why I need it: 30 days is the default but I'll widen or narrow if you want. If missing I ask: "How far back should I look - last 30 days, last quarter, since launch?"
- Segment filter - Optional. Why I need it: lets me cluster by customer type instead of mixing everything. If you don't have it I keep going with TBD and surface mixed clusters.
Steps
- Read
context/support-context.md. For current positioning + VIP list. If missing, runset-up-my-support-infofirst.
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 · 120 lines · 64 tokens per session scan A 6bb24996cfae
mine-my-tickets is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 1,387 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-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'.