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 tune-my-routinggit 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/tune-my-routing)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/tune-my-routing"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/tune-my-routing/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/tune-my-routing"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/tune-my-routing.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.00065 | $0.00961 |
| Opus 5 | $0.00032 | $0.00481 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
tune-my-routing 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tune My Routing
When to use
- "update our routing" / "fix routing" / "what's bug vs feature request."
- "we moved to {tracker}" / "refunds now go to {person}" / "add new tier."
- When
review-my-support scope=weeklysurface classification drift.
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.
- Dev tracker (GitHub / Linear) - named target for the bug routing rule. Required if bug routing chains into a tracker.
- Billing (Stripe) - named target for billing routing. Optional.
- Docs / notes (Notion / Google Docs) - named target for KB or status routing. Optional.
If you want bugs to flow into a tracker I stop and ask you to connect the one you actually use.
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 routing categories - Required. Why I need it: I rewrite from your existing rules, not from scratch. If missing I ask: "What buckets do you sort tickets into today - bug, how-to, billing, anything else?"
- What's changing - Required. Why I need it: I won't rewrite the whole section if you only meant to update one rule. If missing I ask: "What part of routing do you want to change - the tracker, the categories, who approves refunds, something else?"
- Refund approver - Optional. Why I need it: billing rule names a real human. If you don't have it I keep going with TBD and leave it as "founder approves."
Steps
-
Read
context/support-context.md. If missing, runset-up-my-support-infofirst. -
Surface current rules to me. Read Routing rules section, restate in 3–4 lines ("today: bug → Linear, feature request →
requests.json, outage →playbooks/p1-outage.md, billing → Stripe + you approve refunds"). Ask: what changing?
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 · 68 lines · 65 tokens per session scan A cf404dda4597
tune-my-routing is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 65 tokens to every session and 961 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
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.