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 commands/vmobifystudio/app-dev-team/app-dashboardgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00022 | $0.01269 |
| Opus 5 | $0.00011 | $0.00634 |
| Sonnet 5 | $0.00004 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
app-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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-dashboard — The diagnostic dashboard
A projection of docs/, served on localhost:4173. It never writes state: where it acts, it
invokes the same validated CLI the agents use and shows you the command and its exit code.
Which of the two this is
There are two dashboards, permanently, and neither replaces the other.
This one — /app-dashboard |
/app-control-room |
|
|---|---|---|
| What it is | the emergency / diagnostic interface | the product |
| Dependencies | zero — one file, Node stdlib, no build step | React + TypeScript + Vite in control-room/, with its own package.json |
| Shape | eight ranked panels, cause first | five screens: Mission Control · Communications · Board · Team · Founder Inbox |
| Reach for it when | the build stack is broken, npm install fails, or you need one shareable file |
day to day — following threads, reading the roster, working the founder inbox |
Never make the only diagnostic tool depend on the stack it may need to diagnose. That is why
this one has no dependencies and why it is not going away. Both use the same action whitelist
(scripts/lib/actions.mjs) and the same read layer (scripts/lib/project.mjs), so they cannot
disagree about one board.
Steps
-
Start it from the project root:
node "${CLAUDE_PLUGIN_ROOT}/scripts/studio-dashboard.mjs" --project . --port 4173Print the URL it emits and stop. Do not summarise the panels — the page is the output, and a summary of a live page is stale the moment it is written.
Flags:
--port Nif 4173 is taken ·--no-actionsfor a strictly read-only session. -
Or export a static copy to share with someone who will not run a server:
node "${CLAUDE_PLUGIN_ROOT}/scripts/studio-dashboard.mjs" --project . --export docs/34-dashboard.htmlOne self-contained file: the state is baked in, there is no server, and the action buttons are absent because a file on disk cannot invoke a CLI. It is a snapshot — it carries its generation timestamp in the header for exactly that reason. Regenerate it, never hand-edit it.
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.
- 2d ago First seen · 95 lines · 22 tokens per session scan A 66be061bf5a6
app-dashboard is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 1,269 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-31.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
factory-next
Recommend and optionally run the next factory stage for this repo.
compose-preview
Generate and verify Compose previews for UI components.
android-build
Build Android project with Gradle, fix errors, generate APK/AAB. Invokes android-build-resolver for issues.
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.