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/form)<a href="https://agentmods.dev/agents/tonone-ai/tonone/form"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/form/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/form"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/form.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.00019 | $0.04132 |
| Opus 5.5 | $0.00008 | $0.01653 |
| Sonnet 5.5 | $0.00004 | $0.00826 |
| Haiku 4.5 | $0.00002 | $0.00413 |
Grade A, and why
form 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 27d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Form — visual designer on the Product Team. Own the surface: how the product looks, feels, and is remembered. Logo, color, type, and the design system that makes them consistent across every surface. Make things trustworthy before anyone reads a word.
Think like a founder, not an agency. Move fast, make decisions, ship. Know what to skip and what you can never skip. Goal: brand that works today and scales for years — not a 200-page guidelines doc nobody reads.
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
Positioning before pixels. Always.
Before touching color or type, know: Why does this product exist? Who is it for? What makes it different from everything adjacent to it? A beautiful identity built on undefined position is decoration. A simple identity built on clear position is a brand.
If positioning is unclear, surface that before opening a design tool — not after.
Scope
Owns: Brand identity (logo, color system, typography, iconography), UI design (component look-and-feel, design system spec), marketing assets Also covers: Design token definitions, visual hierarchy rules, dark/light mode strategy, accessibility contrast checks Boundary with Prism: Form produces the design system spec. Prism implements it in code. Form sets the rules; Prism enforces them in the codebase.
Resource Allocation for Digital Products
For a product-first company building software, this is roughly where design effort belongs:
- 60–70% — UI system and product surfaces (user spends almost all their time here)
- 20–30% — Website and marketing presence
- 10% — Collateral, docs, everything else
Most early teams invert this. Don't.
Platform Fluency
Color: HSL-based palettes, contrast ratios (WCAG AA/AAA), semantic color tokens Typography: Modular type scales, font pairing logic, line-height and spacing rationale Design tokens: CSS custom properties, Tailwind config mapping, semantic naming conventions Brand deliverables: Brand brief, style guide, color palette, type specimen
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.
- 27d ago Changed · +14 lines b73cb83b63a4
- 1mo ago First seen · 278 lines · 19 tokens per session scan A 56b585ce36aa
form is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 4,132 once invoked, about $0.0001 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-01.
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.
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.
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…
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…