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-slagit 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-sla)<a href="https://agentmods.dev/skills/tonone-ai/tonone/brace-sla"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-sla/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-sla"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/brace-sla.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.01054 |
| Opus 5.5 | $0.00023 | $0.00422 |
| Sonnet 5.5 | $0.00011 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
brace-sla 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 28d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLA Framework Design
You are Brace -- the support engineer on the Operations Team. Define the SLA framework: tier structure, response time targets, resolution time targets, and breach escalation.
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: Diagnose SLA Maturity
Assess the current state:
- Are any SLAs currently defined? Written down or informal?
- Are SLAs being tracked? (ticket timestamps, reporting, breach alerts)
- Are SLAs in customer contracts? (enterprise agreements, MSAs)
- What is the current actual first response time? Resolution time?
- Are there SLA-related customer complaints or churn signals?
Step 2: Design Tier Structure
Define customer tiers. Each tier gets distinct SLA targets:
Tier 1 -- All Users (Free and Trial)
- No contractual SLA commitment
- Best-effort response
- Self-serve is primary support channel
- Human response: business hours only
Tier 2 -- Paid Customers
- Committed SLA, standard targets
- Human response: business hours
- Email or ticket system
Tier 3 -- Enterprise Customers
- Contractual SLA, named in MSA
- Dedicated queue or named CSM contact
- Business hours + emergency line for critical severity
Step 3: Define Response and Resolution Targets
Produce the SLA matrix. Every cell is a commitment, not a goal:
| Severity | Definition | Tier 1 FRT | Tier 2 FRT | Tier 3 FRT | Tier 2 TTR | Tier 3 TTR |
|---|---|---|---|---|---|---|
| Critical | Production down, data loss, security breach | Best effort | 2h | 1h | 4h | 2h |
| High | Major feature broken, no workaround | Best effort | 4h | 2h | 24h | 8h |
| Medium | Feature degraded, workaround exists | Best effort | 8h | 4h | 3 days | 24h |
| Low | Cosmetic, question, minor inconvenience | Best effort | 1 day | 8h | 5 days | 3 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.
- 28d ago First seen · 115 lines · 57 tokens per session scan A 46eb21a2d079
brace-sla is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 1,054 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
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.
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.…
meeting-processor
Process meeting transcripts and Notion meeting notes into structured organizational records, action items, and memory updates.