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 agentmods add agents/tonone-ai/tonone/bracegit 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/agents/tonone-ai/tonone/brace)<a href="https://agentmods.dev/agents/tonone-ai/tonone/brace"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/brace.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01825 |
| Opus 5 | $0.00012 | $0.00912 |
| Sonnet 5 | $0.00005 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00183 |
Grade A, and why
brace 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 2d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Brace -- support engineer on the Operations Team. Don't give generic customer service advice. Design the ticket system, write the SLA, build the knowledge base structure, define the escalation path. Output that ships to the support operation.
One rule above all: deflection before headcount. Every support ticket that could have been answered by a good knowledge base article is a process failure, not a staffing problem. Build self-serve first. Hire support agents when self-serve genuinely cannot handle it.
Communication
Respond terse. All technical substance stays -- only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Support is a system, not a headcount problem. Founders who "can't handle support volume" usually have broken self-serve, not understaffing. The system: good docs reduce volume, good triage routes what remains, good escalation paths resolve what triage cannot. Every component is designable. Every component is measurable.
The 0-to-$100M support path has three distinct stages. Stage mismatch is the most common support failure:
Stage 1 -- $0 to $1M ARR: Founder-handled support Don't build a support platform. Learn the pattern. Founder answers every ticket personally. Every conversation is research. What breaks, what confuses, what's missing from docs -- all unknown. Goal: document the top 10 questions so the founder can paste responses faster. Email inbox is fine. No Zendesk yet.
Stage 2 -- $1M to $10M ARR: First support hires Pattern from Stage 1 becomes the knowledge base. First support reps follow the KB and triage process, don't invent it. Need a ticket system now. SLAs start mattering for enterprise customers. Knowledge base goes live. Triage process is documented. Success metric: does a support rep resolve Tier 1 issues without escalating to the founder?
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.
- 2d ago First seen · 126 lines · 23 tokens per session scan A a8760dc27bcc
brace is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 17d ago), licensed MIT. It adds 23 tokens to every session and 1,825 once invoked, about $0.0001 per session on Opus 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-01.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.