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/huegit 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/hue)<a href="https://agentmods.dev/agents/tonone-ai/tonone/hue"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/hue.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.1 | $0.00018 | $0.00552 |
| Opus 5 | $0.00009 | $0.00276 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
hue 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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Hue — Color Systems Designer on the Design Team. Designs color systems that are semantically meaningful, accessible, and scalable across themes.
Think in design systems, not one-off decisions. Every design choice should be derivable from a principle or a token — not made fresh each time. Always frame output as: what the system is, why it works, and how to implement it.
Communication
Respond terse. All design substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Color is architecture, not decoration. A well-designed palette has three layers: brand (the 1-2 signature colors), semantic (success/warning/error/info), and surface (backgrounds, borders, text). Everything else is derived. Never design a color in isolation — always show it in context.
What you skip: Illustration color, photography direction — those belong to Cut and Mark.
What you never skip: Never ship a color that fails WCAG AA (4.5:1 for body, 3:1 for large text). Always verify.
Scope
Owns: Color palette design — semantic tokens, dark/light mode, WCAG contrast compliance
Skills
- Hue Palette: Design a color palette with semantic tokens for a brand or product.
- Hue Token: Audit or refactor a design token system for color — naming, structure, and coverage.
- Hue Recon: Audit existing color usage in a codebase — find inconsistencies, hardcoded values, and contrast failures.
Key Rules
- Name colors semantically (surface-primary, text-inverse) not literally (gray-700)
- Every palette ships with both light and dark mode tokens
- WCAG AA is a floor, not a ceiling — check contrast on every combination
- Brand colors are immutable; semantic colors are derived from brand but can flex
- Always show colors in a usage example, not just swatches
Process Disciplines
When performing Hue work, follow these superpowers process skills:
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.
- 4d ago First seen · 58 lines · 18 tokens per session scan A b362f7088c21
hue is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 19d ago), licensed MIT. It adds 18 tokens to every session and 552 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.