Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Abilityai/abilities/plugin install trinityWrote 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/abilityai/abilities/create-dashboard)<a href="https://agentmods.dev/skills/abilityai/abilities/create-dashboard"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/create-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/abilityai/abilities/create-dashboard"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/create-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.00049 | $0.03785 |
| Opus 5.5 | $0.00020 | $0.01514 |
| Sonnet 5.5 | $0.00010 | $0.00757 |
| Haiku 4.5 | $0.00005 | $0.00379 |
Grade B, and why
create-dashboard scanned grade B with 1 finding 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 7d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la .claude/skills/*/SKILL.md 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/trinity:create-dashboard
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.create-dashboard vX.Y — recent: <summary>. Then proceed.
Generate an agent-specific /update-dashboard skill that keeps dashboard.yaml current for Trinity. Analyzes the agent's purpose and data sources, proposes metrics, gets user approval, then creates a schedulable skill.
Trigger
User wants to:
- Add a dashboard to an existing agent
- Create or regenerate dashboard metrics
- "create dashboard", "add dashboard", "setup dashboard"
What This Creates
A new skill at .claude/skills/update-dashboard/SKILL.md that:
- Gathers current metrics from agent data sources
- Writes
dashboard.yamlto/home/developer/dashboard.yaml - Is designed to run on a schedule (e.g., hourly via Trinity cron)
- Uses widget types appropriate for the agent's purpose
PHASE 1: Gather Context
1.1 Read Agent Identity
Read CLAUDE.md (or README.md if no CLAUDE.md exists).
Extract:
- Agent name and purpose
- Primary responsibilities
- Key workflows and capabilities
1.2 Discover Data Sources
Glob for potential data files:
*.json,*.yaml,*.ymlin workspace rootmemory/,data/,logs/,state/directories- Any
*_log.md,*_state.*,*_history.*files
1.3 Inventory Existing Skills
ls -la .claude/skills/*/SKILL.md 2>/dev/null
Note skill names - they indicate what the agent does.
1.4 Check for Existing Dashboard
Read dashboard.yaml if it exists - use current structure as baseline.
PHASE 2: Propose Dashboard Metrics
Based on analysis, propose a dashboard structure. Consider these categories:
Status Metrics (always include)
- Agent Status: Running/Idle/Error state
- Last Activity: When agent last performed work
- Health Check: Any error counts or issues
Activity Metrics (based on agent purpose)
- Task Counts: Items processed, completed, pending
- Progress: Completion percentage for ongoing work
- Throughput: Rate of work (items/hour, etc.)
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.
- 7d ago Changed · +2 lines 295bbd4d2d44
- 24d ago Changed · +41 lines 52a8f47e89fb
- 1mo ago First seen · 363 lines · 49 tokens per session scan B 9fded6d8f84e
create-dashboard is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 3,785 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…