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 buccaneermethodology/ExplorationDashboardSynthesizer --skill exploration-dashboard-synthesizergit clone --depth 1 https://github.com/buccaneermethodology/ExplorationDashboardSynthesizerWrote 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/buccaneermethodology/explorationdashboardsynthesizer/exploration-dashboard-synthesizer)<a href="https://agentmods.dev/skills/buccaneermethodology/explorationdashboardsynthesizer/exploration-dashboard-synthesizer"><img src="https://agentmods.dev/badge/skills/buccaneermethodology/explorationdashboardsynthesizer/exploration-dashboard-synthesizer/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/buccaneermethodology/explorationdashboardsynthesizer/exploration-dashboard-synthesizer"><img src="https://agentmods.dev/badge/skills/buccaneermethodology/explorationdashboardsynthesizer/exploration-dashboard-synthesizer.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.00078 | $0.01064 |
| Opus 5 | $0.00039 | $0.00532 |
| Sonnet 5 | $0.00016 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
exploration-dashboard-synthesizer 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 11d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploration Dashboard Synthesizer
Purpose
Use this skill to turn messy exploration material into an initial BM-style Exploration Dashboard. The Dashboard is a cognitive coordination artifact, not a narrative summary: prefer faithful structuring, visible uncertainty, and actionable exploration units.
Use $dashboard-governance instead when a repository already has a Dashboard and the task is to maintain task state, mark sessions complete, record decisions, or identify emergent next sessions after project work.
Workflow
- Identify the input scope: meeting notes, brainstorming fragments, docs, article text, AI conversation history, or mixed material.
- Extract major themes and cluster them into Big Ideas. Use multiple Big Ideas when directions are meaningfully different.
- Convert concrete fragments into Sessions under the relevant Big Idea. Set a new candidate to lifecycle Status
todoonly when projecting into a governed repository; usedecision-neededonly for a real pending choice and reference its Decision. - Classify each Session as
Exploration,Knowledge, orProposed. - Summarize supported insights under Key Points and future options under Next Suggestions.
- Preserve uncertainty with Assumptions and Unresolved Questions instead of inventing conclusions.
- Keep the output concise enough to become a working Dashboard.
Session Types
Exploration: a real exploration activity that already happened.Knowledge: an existing knowledge artifact, method, metric, concept, or reusable module.Proposed: a suggested exploration topic that could become a future Session.
Only Exploration Sessions contribute to Big Idea Length. Use Unknown when a length or coverage estimate is not supported by the input. Use - or N/A for Knowledge and Proposed Session length.
Output Format
# Exploration Dashboard
## Big Idea: [short name; bilingual label optional]
- Big Idea Length: [sum of Exploration Session lengths, or Unknown]
- Coverage: [estimated exploration progress, or Unknown]
- Key Points:
- [major insights already supported by the input]
- Next Suggestions:
- [possible future exploration topics]
### Sessions
| Session ID | Session Type | Topic | Scope | Purpose | Length (minutes) | Key Points |
|------------|--------------|-------|-------|---------|-------------------|------------|
| B1-E1 | Exploration | ... | ... | ... | Unknown | ... |
### Assumptions
- [Only include assumptions needed to interpret ambiguous material. Use "None" if not needed.]
### Unresolved Questions
- [Questions that should not be invented into conclusions. Use "None" if not needed.]
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 79 lines · 78 tokens per session scan A 0c6d242c982d
exploration-dashboard-synthesizer is a skill published in the GitHub repository buccaneermethodology/ExplorationDashboardSynthesizer (6 stars, last pushed 24d ago), licensed MIT. It adds 78 tokens to every session and 1,064 once invoked, about $0.0004 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-31.
Other skills, from other repositories
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
live-dashboard
A Notion-style team dashboard template showing key performance indicators, seven-day trends, recent activity, and a task table. KPI means a measurable indicator of progress or performance.
social-media-matrix
A multi-platform social media tracking dashboard that compares platforms and metrics in a table-like view. It includes charts, an insights panel, and a grid of top posts.
metabase-data-app-semantic-layer
Use when building, creating, or editing data apps that should query Metabase tables and metrics through generated schema files like metabase.data.ts or .metabase.data.ts.
metabase-data-app-actions
Use when a Metabase data app needs to trigger a write or mutation — submitting a form, updating a row, deleting an entry, running a saved action, or any "do something" interaction. Covers invoking an existing action via useAction, parameter typing, response handling, and the critical post-action refresh of any UI data…