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 skills add tonone-ai/tonone --skill prism-dashboardgit 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/skills/tonone-ai/tonone/prism-dashboard)<a href="https://agentmods.dev/skills/tonone-ai/tonone/prism-dashboard"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/prism-dashboard/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/skills/tonone-ai/tonone/prism-dashboard"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/prism-dashboard.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.00044 | $0.01096 |
| Opus 5.5 | $0.00018 | $0.00438 |
| Sonnet 5.5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
prism-dashboard 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build an Internal Dashboard
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Detect Environment
Discover the project's stack and existing admin tooling:
- Check for framework:
next.config.*,nuxt.config.*,svelte.config.*,vite.config.* - Check
package.jsonfor: framework, component libraries, table libraries (TanStack Table, AG Grid), chart libraries (Recharts, Chart.js, D3) - Check for existing admin routes:
admin/,dashboard/,backoffice/directories - Check for API layer: REST endpoints, GraphQL schema, tRPC routes, database access patterns
- Check for auth: existing authentication/authorization setup that the dashboard must integrate with
Step 1: Understand the Dashboard
Before building, clarify:
- What data to show? — which entities, what fields, what relationships
- Who uses it? — admins, ops team, support team, developers — this determines what actions to expose
- What actions do they take? — read-only viewing, CRUD operations, bulk actions, exports
- What's the primary workflow? — list → detail → edit? Search → action? Monitor → respond?
If the user hasn't specified, ask. Internal tools deserve good UX too.
Step 2: Build the Data Table
The data table is the core of most dashboards:
- Columns: define typed columns with appropriate formatters (dates, numbers, status badges, truncated text)
- Sorting: server-side or client-side sorting on relevant columns
- Filtering: practical filters — status dropdowns, date ranges, search text — not a filter for every column
- Pagination: server-side pagination for large datasets — show total count, page size selector
- Row actions: contextual actions per row (view, edit, delete) — use a dropdown menu for more than 2 actions
- Bulk actions: select multiple rows for bulk operations if applicable (delete, export, status change)
- Loading state: skeleton rows while data loads, not a spinner replacing the entire table
- Empty state: helpful message when filters return no results vs. when there's genuinely no data
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 · 111 lines · 44 tokens per session scan A 4ce4cabed8f3
prism-dashboard is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 1,096 once invoked, about $0.0002 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-27.
Other skills, from other repositories
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
outsystems-design-to-app
Beta Feature. This skill is a Beta Feature: a non-final OutSystems capability provided to collect customer feedback. It can change significantly, including through breaking changes, or be discontinued. The first time you use this skill in a conversation, tell the user it's a Beta Feature and share .
software-android-design
Designs and audits native Android interfaces. Use when reviewing Compose layout, typography, color, motion, or adaptive patterns on a verified emulator build.