triage-ticket

triage-ticket is a skill for Claude Code, Codex from osaurus-ai/osaurus. It costs 26 tokens per session (185 once invoked), scanned A, original, MIT.

A fixed-format helper for sorting Acme support tickets. It reads a ticket and its latest comments, then applies Acme's priority rules.

In plain words
What is it for?
Triageing support tickets and producing the required priority, area, next step, and reason.
Why use it?
It gives teammates a consistent priority, product area, and next step without promising a repair date. When multiple rules apply, it chooses the higher priority.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Triageing support tickets and producing the required priority, area, next step, and reason.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/osaurus-ai/osaurus/triage-ticket
About the project

Osaurus is a native macOS application that provides AI agents with memory, tools, autonomous execution, and identity around local or cloud models. It is used by people who want agents to run on their Mac, including fully offline with local models, and the catalogue entry contains an instruction and rule for working with it.

osaurus-ai/osaurus · 8,077 stars · on GitHub · osaurus.ai

Install

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.

Any agent
npx skills add osaurus-ai/osaurus --skill triage-ticket
Clone the repo
git clone --depth 1 https://github.com/osaurus-ai/osaurus

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for triage-ticket

README.md
[![agentmods](https://agentmods.dev/badge/skills/osaurus-ai/osaurus/triage-ticket/github.svg)](https://agentmods.dev/skills/osaurus-ai/osaurus/triage-ticket)
Your own site
<a href="https://agentmods.dev/skills/osaurus-ai/osaurus/triage-ticket"><img src="https://agentmods.dev/badge/skills/osaurus-ai/osaurus/triage-ticket/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.

agentmods 80×15 button for triage-ticket

Your own site · 80×15
<a href="https://agentmods.dev/skills/osaurus-ai/osaurus/triage-ticket"><img src="https://agentmods.dev/badge/skills/osaurus-ai/osaurus/triage-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 185 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00185
Opus 5.5 $0.00010 $0.00074
Sonnet 5.5 $0.00005 $0.00037
Haiku 4.5 $0.00003 $0.00018

Measured today against content hash a83f1a3faf14, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

triage-ticket 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 today.

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.

docs/examples/osaurus-bundle-example/skills/triage-ticket/SKILL.md · 27 lines

What it actually says

Triage a ticket

Use this when the user asks you to triage, prioritize or sort support tickets.

  1. Read the ticket and its latest comments.
  2. Pick the priority from references/priority-matrix.md. When two rows match, take the higher priority.
  3. Name the product area in one or two words.
  4. Write the next step as one sentence a teammate can act on.

Reply with exactly:

Priority: P1|P2|P3|P4
Area: <area>
Next step: <one sentence>
Why: <one sentence that cites the matrix row>

Do not promise the customer a fix date.

Files

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.

Changes

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.

  1. today First seen · 27 lines · 26 tokens per session scan A a83f1a3faf14

Subscribe to this mod's changes

triage-ticket is a skill published in the GitHub repository osaurus-ai/osaurus (8,077 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 185 once invoked, about $0.0001 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-10-24.

Related

Other skills, from other repositories

docs-governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…

affaan-m/ECC · 67 tokens

meeting-action-items

Turn meeting notes into cited decisions, owners, tickets.

NousResearch/hermes-agent · 15 tokens

detecting-pv-signals

Computes disproportionality signals — PRR, ROR, EBGM, and IC (BCPNN) — over FAERS / OpenFDA drug-event data to flag potential safety signals. Use when the user wants to mine spontaneous-report data for drug-reaction associations, build a 2x2 contingency table, compute a Proportional Reporting Ratio or Reporting Odds…

maziyarpanahi/openmed · 218 tokens

evaluating-with-leakage-gates

Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…

maziyarpanahi/openmed · 158 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens

running-openmed-ondevice

Run OpenMed models fully on-device with the MLX (Apple Silicon), CoreML (iOS/macOS), or ONNX/WebGPU (cross-platform/browser) backends, including convert-quantize-run workflows. Use when the user wants to deploy OpenMed at the edge, run NER/de-id on Apple Silicon, target iPhone/iPad/Mac, export to ONNX or WebGPU…

maziyarpanahi/openmed · 175 tokens