agentmods.dev

settings-viewer

A tool that creates and opens a visual dashboard for Claude Code settings and usage analytics. Analytics are information about how the tool has been configured and used.

In plain words
What is it for?
Viewing Claude Code settings, checking usage, and opening either a generated snapshot or a live local dashboard.
Why use it?
It puts configuration and usage information into a browser view instead of requiring you to inspect files or command output.

Skill for Claude CodeCodex

2 6d ago B scan 74 tokens original MIT
View the source file hamchowderr/braynee
Install

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.

agentmods
npx agentmods add skills/hamchowderr/braynee/settings-viewer
Any agent
npx skills add hamchowderr/braynee --skill settings-viewer
Clone the repo
git clone --depth 1 https://github.com/hamchowderr/braynee

Made for: Claude Code, Codex.

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,005 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00074 $0.01005
Opus 5 $0.00037 $0.00502
Sonnet 5 $0.00015 $0.00201
Haiku 4.5 $0.00007 $0.00101

Measured 2d ago against content hash 0c614fc4ed0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

settings-viewer 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 2d ago.

The scan reads SKILL.md. This mod also ships 20 executable files (scripts/dashboard.mjs, scripts/data/beads.mjs, scripts/data/braynee.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

The dashboard can be delivered two ways, selected by the `BRAYNEE_DASHBOARD_MODE` env var (set it in `~/.claude/settings.json` under `env`):
skills/settings-viewer/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Settings Viewer (Braynee Dashboard)

Generates a visual HTML dashboard of the user's Claude Code settings and usage analytics, then opens it in the browser.

How to execute

node "{baseDir}/scripts/dashboard.mjs"

dashboard.mjs opens the dashboard in whichever delivery mode the user has chosen (see below). It defaults to file mode — identical to the old behavior — so this just works out of the box.

Delivery modes

The dashboard can be delivered two ways, selected by the BRAYNEE_DASHBOARD_MODE env var (set it in ~/.claude/settings.json under env):

Mode What happens When to use
file (default) generate.mjs rebuilds ~/.claude/temp/settings-viewer.html and opens it. A fresh static snapshot each run. Simplest; no running process.
server A persistent localhost server (127.0.0.1:7717) serves the dashboard live from a warm cache, refreshing in the background. dashboard.mjs ensures it's up and opens its URL. Always-current data without re-running the slow build; reachable from a browser tab you leave open.

Optional in server mode: BRAYNEE_DASHBOARD_PORT (default 7717), BRAYNEE_DASHBOARD_REFRESH_MS (default 5 min).

Server mode is a singleton — one managed instance shared across all Claude Code sessions (started lazily on first open, kept alive after). It binds 127.0.0.1 only, so it's private to the machine with no inbound exposure.

Viewing inside Obsidian: point the Custom Frames "Braynee" frame at http://127.0.0.1:7717 (server mode) instead of the settings-viewer.html file, so the in-Obsidian tab is always live.

Reaching it from your phone: keep the server bound to localhost and expose it to your own devices over Tailscale with tailscale serve --bg 7717 (tailnet-only HTTPS, never tailscale funnel). No public exposure.

Note: as of the delivery-modes change, the dashboard no longer regenerates on every session start — it's on-demand (this skill) in file mode, and continuously live in server mode.

Read the full file on GitHub · 88 lines

Files

What ships with it

20 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.

Changes

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.

  1. 2d ago First seen · 88 lines · 74 tokens per session scan B 0c614fc4ed0f

Subscribe to this mod's changes

settings-viewer is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 74 tokens to every session and 1,005 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens