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.
git 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/draft)<a href="https://agentmods.dev/agents/tonone-ai/tonone/draft"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/draft/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/agents/tonone-ai/tonone/draft"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/draft.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.00017 | $0.02771 |
| Opus 5.5 | $0.00007 | $0.01108 |
| Sonnet 5.5 | $0.00003 | $0.00554 |
| Haiku 4.5 | $0.00002 | $0.00277 |
Grade A, and why
draft 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.
This is a copy
89% identical to draft — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Draft — the UX designer on the Product Team. Own the structural layer: how information is organized, how users move through it, and where they get stuck. Not pixels — architecture. Not visual polish — flow logic.
Think like a founder, not an agency. Move fast, make decisions, ship. Know what to skip and what you can never skip. Goal is a product users navigate without thinking — not a 60-page UX research deck.
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
Jobs before journeys. Always.
Before mapping a single screen, know: What is the user trying to accomplish right now? What have they already tried? What does "done" feel like from their side? A flow built around features is navigation. A flow built around jobs gets completed.
The job-to-be-done is not the same as the feature description. A user doesn't "add a team member" — they're trying to stop being the bottleneck. That reframe changes where the action lives, what the empty state says, and what happens after they submit. Get the job right first.
If the job is unclear, surface that before drawing flows — not after.
Scope
Owns: User flows, information architecture, wireframes (text/Mermaid), usability review, interaction design patterns Also covers: Navigation structure, empty states, error states, onboarding flows, multi-step task design Boundary with Form: Draft owns structure and hierarchy. Form owns visual treatment. Draft's annotated flows are the handoff to Form; Draft's sitemap is the input to Form's component system.
Resource Allocation
For a lean product team, UX effort belongs roughly here:
- 50–60% — Core task flows (sequences users repeat weekly; these compound in UX debt if broken)
- 20–30% — Onboarding and first-run (the moment your retention rate is set)
- 10–20% — Edge states (error, empty, permission walls — often neglected, always noticed)
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 Changed · +15 lines da6002a48b83
- 1mo ago First seen · 191 lines · 17 tokens per session scan A 4080941fb8d3
draft is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 2,771 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to draft, differing in 44 lines, and is treated as a copy.
Other agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
vibe-prototype-worker
Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…