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 sandbaseai/sandbase-skills --skill ticket-triagegit clone --depth 1 https://github.com/sandbaseai/sandbase-skillsWrote 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/sandbaseai/sandbase-skills/ticket-triage)<a href="https://agentmods.dev/skills/sandbaseai/sandbase-skills/ticket-triage"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/ticket-triage/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/sandbaseai/sandbase-skills/ticket-triage"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/ticket-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.02643 |
| Opus 5.5 | $0.00022 | $0.01057 |
| Sonnet 5.5 | $0.00011 | $0.00529 |
| Haiku 4.5 | $0.00005 | $0.00264 |
Grade A, and why
ticket-triage 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 1mo 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ticket-triage
Use only support, knowledge-base, and project-tracker sources that are actually available and authorized in the host. State clearly when a source was not checked.
Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.
When checking public documentation or known-issue evidence, read the SandBase API map. Resolve the listed capability with sandbase_discover, inspect its returned name with sandbase_inspect, then follow execute_as to call sandbase_run(name: "<returned name>", arguments: { ... }) using only the current schema. For async results, poll sandbase_run_get with the returned run_id within the task budget; report pending or failed runs without automatically resubmitting them.
Usage
/ticket-triage <ticket text, customer message, or issue description>
Examples:
/ticket-triage Customer says their dashboard has been showing a blank page since this morning/ticket-triage "I was charged twice for my subscription this month"/ticket-triage User can't connect their SSO — getting a 403 error on the callback URL/ticket-triage Feature request: they want to export reports as PDF
Workflow
1. Parse the Issue
Read the input and extract:
- Core problem: What is the customer actually experiencing?
- Symptoms: What specific behavior or error are they seeing?
- Customer context: Who is this? Any account details, plan level, or history available?
- Urgency signals: Are they blocked? Is this production? How many users affected?
- Emotional state: Frustrated, confused, matter-of-fact, escalating?
2. Categorize and Prioritize
Using the category taxonomy and priority framework below:
- Assign a primary category (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category
- Assign a priority (P1–P4) based on impact and urgency
- Identify the product area the issue maps to
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed d482ae3cccf1
- 1mo ago First seen · 282 lines · 54 tokens per session scan A cd1a1fe9880d
ticket-triage is a skill published in the GitHub repository sandbaseai/sandbase-skills (203 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,643 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
notion-meeting-notes
Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.
dsh-skill-dev
A specialist review agent for software that handles purchasing, suppliers, payments, or spending approvals.
bonsai-automation
Automate Bonsai tasks via Rube MCP (Composio). Always search tools first for current schemas.
bugherd-automation
Automate Bugherd tasks via Rube MCP (Composio). Always search tools first for current schemas.
linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.