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 agentmods add skills/gideondk/strata/dashboardnpx skills add gideondk/strata --skill dashboardgit clone --depth 1 https://github.com/gideondk/strataWrote 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/gideondk/strata/dashboard)<a href="https://agentmods.dev/skills/gideondk/strata/dashboard"><img src="https://agentmods.dev/badge/skills/gideondk/strata/dashboard.svg" alt="Measured on agentmods" 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 | $0.00119 | $0.00667 |
| Opus 5 | $0.00060 | $0.00333 |
| Sonnet 5 | $0.00024 | $0.00133 |
| Haiku 4.5 | $0.00012 | $0.00067 |
Grade A, and why
strata: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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:dashboard
A single-page snapshot of vault state. Same content lives in INDEX.md
(renders natively in Obsidian) and gets emitted into the conversation
when you invoke this skill.
How
Two paths depending on freshness needs:
Quick (read what's on disk)
"${CLAUDE_PLUGIN_ROOT}/bin/run-python.sh" -c "
import sys
sys.path.insert(0, '${CLAUDE_PLUGIN_ROOT}/scripts')
from lib import memory_dir
print((memory_dir() / 'INDEX.md').read_text())
"
Use when you trust the cached state (it was regenerated on the last Write). 95% of cases.
Fresh (regenerate first)
"${CLAUDE_PLUGIN_ROOT}/bin/strata" dashboard
dashboard.py rebuilds the content from live data (db, code_graph,
commit_graph) without writing INDEX.md. Slightly slower.
What you'll see
| Section | Source | What it tells you |
|---|---|---|
| Scope counts | Filesystem | Episodic / semantic / procedural sizes |
| Recent activity | mtime, last 7d | What's been written or updated |
| Stale-proposed ADRs | db.stale_decisions |
ADRs in proposed >14d — need closure |
| Drifted notes | code_graph.find_drifted_notes |
Structural + temporal drift |
| Hot files | commit_graph.hotspots |
Top-churn files last 90d |
| ADR implementations | commit_graph.adr_implementations |
Which decisions became code |
| Active PR contexts | pr-context/ subdirs |
In-flight branches |
| Suggested actions | Composed from above | Concrete next steps |
Why this is the dashboard
The vault is markdown on disk. Obsidian renders it. Sync clients
Distribute it. Teammates see updates as files change. We don't need
A web server. We don't run a port. The synced INDEX.md IS the
Dashboard, open Obsidian, get the view.
Don't do
- Don't try to render this as HTML / charts / images. The whole point is that markdown + the user's existing tools win.
- Don't suggest installing a web UI. Open Obsidian on the vault instead, it has graph view, backlinks, search, all native.
- Don't paste the full dashboard in a turn if the user asked something narrow ("how many decisions?"), answer narrowly, leave the dashboard for "show me the state."
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.
- 4d ago First seen · 68 lines · 119 tokens per session scan A 3a998bf626fb
strata:dashboard is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 119 tokens to every session and 667 once invoked, about $0.0006 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
my-wiki
Manage local OKF-compatible Markdown My Wiki vaults with an AI agent. Use for capturing webpages, PDFs, Office documents, notes, images, folders, and ZIP bundles as References; maintaining Reference-to-Concept evidence links; searching or answering from a vault; checking or repairing vault health; switching among…
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
memory-forest
Build, validate, index, and query a private local Memory Forest with provenance-aware layers, pointer-first search, and validated root-first retrieval. Use when creating a new forest, checking an existing forest's structure, building its local SQLite index, or retrieving bounded memory trails without exposing full…
memory-forest-retrieve
Integrate a mandatory, metadata-only Memory Forest consultation gate before an agent responds to each non-empty user-authored text turn.
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or…
wiki-sync
Synthesize a single source note into the vault's wiki/ folder — read the source, find or create the right wiki entry, write it back with proper frontmatter and source links. Used by Lumina's background wiki manager when a note changes.