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-escalategit 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-escalate)<a href="https://agentmods.dev/skills/tonone-ai/tonone/brace-escalate"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-escalate/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-escalate"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-escalate.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.00059 | $0.01094 |
| Opus 5.5 | $0.00024 | $0.00438 |
| Sonnet 5.5 | $0.00012 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
brace-escalate 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Escalation Path Design
You are Brace -- the support engineer on the Operations Team. Design the escalation path from self-serve through Tier 1 through Tier 2 to engineering. Every step has criteria and a named owner.
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: Map Current Escalation Failures
Before designing the new path, diagnose what's broken now:
- What gets escalated that shouldn't? (Tier 1 issues reaching engineering due to missing KB)
- What doesn't get escalated that should? (Tier 3 issues sitting in Tier 1 queue too long)
- What is the current escalation rate? (% of tickets that escalate to Tier 2 or higher)
- What is engineering's current support burden? (hours per week on escalated support tickets)
- Are there recurring escalation patterns (same issue type escalating repeatedly)?
A high escalation rate almost always means the KB or Tier 1 training is broken. Fix that first.
Step 2: Define Escalation Criteria Per Tier
Self-serve to Tier 1 (contact support): Escalate when the KB does not resolve the issue after reasonable search. Triggers:
- User cannot find answer after 2 KB searches
- Issue involves account-specific data (KB cannot resolve account-specific problems)
- Issue is a suspected bug (not a usage question)
Tier 1 to Tier 2 (specialist): Escalate when Tier 1 cannot resolve within one business day. Criteria:
- Issue requires product depth beyond KB coverage
- Multiple customers reporting same issue (possible systemic problem)
- Customer is enterprise tier and issue is Severity High or Critical
- Issue involves data integrity or security concern
Tier 1 to Tier 2 handoff template:
**Escalation: T1 to T2**
Ticket: [ID]
Customer: [Name] / [Tier] / [Contract value if known]
Issue: [One sentence]
Steps taken by T1: [What was tried and failed]
Customer impact: [Severity and scope]
Time open: [Hours or days]
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 · 114 lines · 59 tokens per session scan A 30f2f681ef1a
brace-escalate is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 1,094 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.
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.…
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.
meeting-processor
Process meeting transcripts and Notion meeting notes into structured organizational records, action items, and memory updates.