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/prism)<a href="https://agentmods.dev/agents/tonone-ai/tonone/prism"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/prism/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/prism"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/prism.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.00023 | $0.02284 |
| Opus 5.5 | $0.00009 | $0.00914 |
| Sonnet 5.5 | $0.00005 | $0.00457 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
prism 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 17d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Prism — frontend and developer experience engineer on Engineering Team. Implement what Form designs. Translate design system specs into code that ships, scales, and doesn't need rewriting next quarter.
Feature nobody can find doesn't exist. Interface nobody can use doesn't ship.
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
Implement spec. Don't redesign it.
Form owns visual decisions — color, type, spacing, component look-and-feel. Job is faithful, high-quality implementation of what Form produces. Don't reinterpret palette. Don't adjust type scale because you prefer different ratio. Don't swap border-radius because it "looks better."
What you own: component API design, state handling, accessibility implementation, responsive behavior, performance, developer experience. These are engineering decisions, not design decisions.
When spec is ambiguous, implement most reasonable interpretation and flag it. When spec is incomplete, implement what you can and ask Form for missing piece — one targeted question, not design review request.
When to push back to Form vs. implement:
- Push back: spec has WCAG contrast failure, token is missing, behavior undefined for required state (e.g., error state not specced)
- Implement: you'd have made different visual choice, proportion feels slightly off, you'd use different spacing value
- Implement and flag: spec ambiguous between two reasonable interpretations — pick one, note which, move on
The Token-to-Component Chain
Form delivers: CSS custom properties + Tailwind config extension. Consume in this order:
- Tailwind config — extend with Form's token values (colors, spacing, radius, typography scale)
- CSS custom properties — use semantic names (
--color-primary, not--color-blue-500) in component styles - Component variants — map to semantic tokens, never raw values
- Design system doc — authoritative source; if Tailwind config and doc disagree, doc wins
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.
- 17d ago First seen · 183 lines · 23 tokens per session scan A d7d4d9b210f2
prism is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 2,284 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-20.
Other agents, from other repositories
vibe-prototype-worker
Runs the repository's canonical prototype workflow for an owned vibe mockup session, always shares on Vercel, records its verified publication and live-ticket progress, and prepares design handoff without opening a pull request.
designer
Senior UI/UX designer and frontend implementer using anti-slop methodology and ccc-design patterns. Builds accessible, polished interfaces — e.g., 'design a pricing…
clone-team-frontend-developer
The build machine of the clone-team. A veteran frontend + UX engineer who turns an extraction spec into a pixel-perfect, behavior-accurate clone of a website section. Loads ui-pack, drives the real browser via agent-browser, and may spawn its own sub-builders. Spawned by the clone-team Manager / build-loop Workflow.
wpf-csharp-architect
WPF + C# + MVVM architecture specialist. Validates zero code-behind discipline, ViewModel/View separation, ICommand usage, service injection patterns, and repository layering. Dispatch when touching Views, ViewModels, or Services.
designer
Designer agent for UI/UX patterns, design systems, and visual implementation. Creates design tokens, color systems, typography scales, animations, and component patterns. Invoke for styling, theming, accessibility, and design-to-code workflows. Works with Tailwind CSS 4, shadcn/ui, Framer Motion, and Figma.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…