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 catch-me-up-on-a-threadgit 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/catch-me-up-on-a-thread)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/catch-me-up-on-a-thread"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/catch-me-up-on-a-thread/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/catch-me-up-on-a-thread"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/catch-me-up-on-a-thread.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.00062 | $0.00652 |
| Opus 5 | $0.00031 | $0.00326 |
| Sonnet 5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
catch-me-up-on-a-thread 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catch Me Up on a Thread
When to use
conversations/{id}/thread.json has >handful of messages, need context fast. Typical triggers:
- You: "what's the story with the Acme thread?"
- Reopen conversation dormant >3 days.
- Before
draft-a-replyon thread with 5+ messages - run first, draft better.
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 / Outlook) - pull the live thread if it's not already in
conversations.json. Optional. - Support helpdesk (Intercom / Zendesk / Help Scout) - alternate thread source. Optional.
I keep going against the local thread index if neither is connected, but I'll tell you the summary may be missing the latest reply.
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.
- Which thread - Required. Why I need it: I summarize one specific conversation, not "support in general." If missing I ask: "Which conversation should I summarize - share the customer's name or the latest subject line?"
- Audience for the summary - Optional. Why I need it: a 3-bullet for you reads differently than a handoff for a teammate. If you don't have it I keep going with TBD and write it for your eyes.
Steps
- Load
conversations/{id}/thread.jsonand index row fromconversations.json. - Walk thread chronologically. Note: customer's original ask, scope changes, every promise made, every answer given.
- Produce exactly three bullets:
- Where we are - last message, sender, current state (waiting on customer / waiting on us / drafting).
- What we promised - outstanding commitments. Pull from
followups.jsonfiltered by conversation, plus uncaptured promises in thread (recommendtrack-my-promisesif found). - What customer expects next - most recent explicit or implied ask.
- Append summary as dated block in
conversations/{id}/notes.md- persisted for next time.
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 · 48 lines · 62 tokens per session scan A de8f794d5372
catch-me-up-on-a-thread is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 62 tokens to every session and 652 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
inbox-zero
Scan your support inbox and batch-process tickets with quick actions (reply, tag, assign, close).
ticket-summarize
Summarize a support ticket thread into key points and action items.
weekly-digest
Generate a weekly support digest and post it to Slack.
zoho-desk-triage
Pull open tickets from Zoho Desk and triage by priority and department.
Escalation Handler
Handle escalated support issues with structured triage, communication, and resolution processes.
Support Responder
Expert customer support specialist delivering exceptional customer service, issue resolution, and user experience optimization. Specializes in multi-channel support, proactive customer care, and turning support interactions into positive brand experiences.