Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. 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/egregore-labs/egregore/main/.claude/skills/dashboard/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/dashboard)<a href="https://agentmods.dev/skills/egregore-labs/egregore/dashboard"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/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/egregore-labs/egregore/dashboard"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 160 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00466 |
| Opus 5.5 | $0.00020 | $0.00186 |
| Sonnet 5.5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
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 24d 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
Dashboard
Use this bounded status card only when the user explicitly asks for Dashboard
or the whole personal overview. A request to return to one earlier piece of
work must use attached EGREGORE_ORG_CONTEXT_V1 evidence or exactly one Search
workflow query when that evidence is absent. Never use Dashboard as discovery
fallback.
Render the personal view immediately. The renderer's stdout IS the product card: it is fully visible the moment rendering finishes, and it must appear exactly once in the conversation. Never copy, regenerate, summarize, or repeat the card — or any of its rows — in your reply; add nothing beyond an answer to something the user separately asked.
Map the requested range to P1D, P7D, P30D, or P365D as {time-range},
then fetch and render exactly one authorized Runtime snapshot:
bash bin/dashboard-data.sh '{time-range}' 2>/dev/null \
| bash bin/node-run.sh bin/codex-skill-render.mjs dashboard-card -
Do not sync repositories, query memory again, or call implementation infrastructure directly. The snapshot owns actor resolution, authorization, bounds, canonical lifecycle state, and presentation data.
Connected enrichment is separate and explicit. Set
EGREGORE_STATUS_CONNECTED_ENRICH=1 only when the user requests projected
Connected status. It is capability/permission gated and cannot replace
canonical handoffs, questions, quests, todos, sessions, or lifecycle metadata.
Never print raw JSON or narrate routine commands. Preserve the shared
72-column card, omit graph/setup messaging in Local mode, end with What's next?, and act on the reply in the next turn.
When to invoke
Explicit personal-status surface for /dashboard or a direct request for the whole personal overview. Do not use it to find or resume one specific prior handoff, project, or work thread; that is semantic organizational recall through Runtime/QMD.
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.
- 24d ago Changed · -230 lines · +13 tokens per session e0eaee8a9062
- 1mo ago First seen · 274 lines · 36 tokens per session scan A 46225f03d4bf
dashboard is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 466 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-08-30.
Other skills, from other repositories
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
gws-calendar
Google Calendar: Manage calendars and events.
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
gws-gmail-watch
Gmail: Watch for new emails and stream them as NDJSON.
gws-gmail
Gmail: Send, read, and manage email.