Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/skills/are-dashboard/SKILL.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/are-dashboard)<a href="https://agentmods.dev/skills/geoloeg-ist/agents-reverse-engineer/are-dashboard"><img src="https://agentmods.dev/badge/skills/geoloeg-ist/agents-reverse-engineer/are-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/geoloeg-ist/agents-reverse-engineer/are-dashboard"><img src="https://agentmods.dev/badge/skills/geoloeg-ist/agents-reverse-engineer/are-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.00017 | $0.00491 |
| Opus 5 | $0.00009 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
are-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 9d 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.
What it actually says
Show the ARE telemetry dashboard with cost analysis, token usage, and trace timelines.
- Run ONLY the exact command shown:
npx agents-reverse-engineer@$VERSION dashboard $ARGUMENTS - DO NOT add ANY flags the user did not explicitly type
- If user typed nothing after
/are-dashboard, run with ZERO flags
Steps
-
Read version: Read
.claude/ARE-VERSION→ store as$VERSION. Show the user:agents-reverse-engineer v$VERSION -
Run the dashboard command:
npx agents-reverse-engineer@$VERSION dashboard $ARGUMENTS -
Present the output to the user. The dashboard has several modes:
- Default (no flags): Shows a summary table of all runs with costs, tokens, duration, and errors
--run <id>: Drill-down into a specific run showing per-entry details (latency, tokens, cost per file)--trace <id>: ASCII Gantt timeline showing concurrent phase execution and worker utilization--trends: Cost and usage trends across all runs (daily aggregation, cache savings, error rates)--format html: Generate a self-contained HTML report with Chart.js visualizations — pipe to a file:npx agents-reverse-engineer dashboard --format html > report.html--format json: Output raw run log data as JSON
-
If no runs found, suggest the user run
/are-generateor/are-updatefirst to create telemetry data.
Options:
--run <id>: Show per-entry detail for a specific run (partial timestamp match)--trace <id>: Show ASCII timeline from a trace file (partial timestamp match)--trends: Show cost & usage trends across all runs--format html: Generate self-contained HTML report with charts--format json: Output raw data as JSON
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.
- 9d ago First seen · 43 lines · 17 tokens per session scan A 677e1723cbe2
are-dashboard is a skill published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 491 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-08-30.
Other skills, from other repositories
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
proxmox-full
Complete Proxmox VE hypervisor management via REST API - VMs, containers, snapshots, backups, storage.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
performance-optimizer
Use for slow endpoints, p95/p99 latency, database query issues, frontend bundle/render performance, memory leaks, caching, profiling, or performance regressions.