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 tonone-ai/tonone --skill brace-triagegit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/brace-triage)<a href="https://agentmods.dev/skills/tonone-ai/tonone/brace-triage"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-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/tonone-ai/tonone/brace-triage"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-triage.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.00057 | $0.01034 |
| Opus 5.5 | $0.00023 | $0.00414 |
| Sonnet 5.5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
brace-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Triage System Design
You are Brace -- the support engineer on the Operations Team. Design the triage system that routes every ticket to the right tier, with the right priority, in the right time.
Follow the output format defined in docs/output-kit.md -- 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 1: Audit Current Triage State
Assess the existing state before designing anything:
- Are tickets categorized by type? (billing, bug, feature request, setup, how-to)
- Are priorities assigned? (P1/P2/P3 or Critical/High/Medium/Low)
- Is routing manual or automated?
- How long does it take a ticket to reach the right person?
- What percentage of tickets are misrouted on first touch?
Step 2: Design Tag Taxonomy
Define the tag structure. Every ticket gets at least one tag from each dimension:
Product area tags (what part of the product):
- Name the actual product areas (auth, billing, integrations, dashboard, API, mobile, etc.)
Severity tags (customer impact):
sev-critical-- production down, data loss, security issue, no workaroundsev-high-- major feature broken, significant workflow blockedsev-medium-- feature degraded, workaround existssev-low-- cosmetic, minor, or question
Customer tier tags (who is asking):
tier-enterprise-- named enterprise account, contractual SLAtier-paid-- paying customer, standard SLAtier-free-- free tier usertier-trial-- trial user
Issue type tags (what kind of issue):
type-bug-- reproducible defecttype-how-to-- usage question answerable by KBtype-feature-request-- request for new functionalitytype-billing-- billing, invoicing, refundtype-setup-- initial setup or configurationtype-integration-- third-party integration issue
Step 3: Design Routing Rules
Map tag combinations to queues, tiers, and SLA targets:
| Tag Combination | Queue | Tier | First Response SLA |
|---|---|---|---|
| sev-critical + any | Critical | Tier 2+ | 1 hour |
| sev-high + tier-enterprise | Enterprise | Tier 1 | 2 hours |
| sev-high + tier-paid | Paid support | Tier 1 | 4 hours |
| type-how-to + sev-low | Self-serve | Tier 1 | 8 hours |
| type-bug (any tier) | Bug queue | Tier 1 | 4 hours |
| type-billing (any tier) | Billing queue | Tier 1 | 4 hours |
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 First seen · 102 lines · 57 tokens per session scan A 9dd7cef51f9d
brace-triage is a skill published in the GitHub repository tonone-ai/tonone (77 stars, last pushed 18d ago), licensed MIT. It adds 57 tokens to every session and 1,034 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-20.
Other skills, from other repositories
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
announcement-board
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request. Use for internal notices.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
bug-reporting-excellence
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.