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.
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/commands/blackbelttechnology/pi-agent-dashboard/dashboard-list-models)<a href="https://agentmods.dev/commands/blackbelttechnology/pi-agent-dashboard/dashboard-list-models"><img src="https://agentmods.dev/badge/commands/blackbelttechnology/pi-agent-dashboard/dashboard-list-models/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/commands/blackbelttechnology/pi-agent-dashboard/dashboard-list-models"><img src="https://agentmods.dev/badge/commands/blackbelttechnology/pi-agent-dashboard/dashboard-list-models.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.00018 | $0.00290 |
| Opus 5 | $0.00009 | $0.00145 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
dashboard-list-models 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 5d 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
Use the pi-dashboard skill (see ../SKILL.md). Discover the base URL: prefer the $PI_DASHBOARD_PORT or $DASHBOARD_PORT env var, else read the port from ~/.pi/dashboard/config.json (default 8000); BASE="http://localhost:$PORT". When auth is enabled, include the JWT cookie.
Task: GET $BASE/api/models. If the argument is annotated (or 1), GET $BASE/api/models?annotated=1 instead. The response is { "object": "list", "data": [...] } where each row is { id: "provider/modelId", provider, reasoning?, input?, contextWindow?, maxTokens?, cost? }. In annotated mode each row also carries excludedReason (null = reachable, no-credential or oauth-incompatible = why it is not). Report the rows (id + provider + key capabilities; in annotated mode note the excludedReason for unreachable ones).
IMPORTANT: never parse ~/.pi/agent/providers.json or ~/.pi/agent/models.json for model inventory — those files hold roles/presets/custom entries, NOT the reachable catalogue, and a parse returns empty (silent failure). GET /api/models is the only correct model-introspection surface.
Arguments (optional annotated):
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.
- 5d ago First seen · 11 lines · 18 tokens per session scan A 094ecc85a2fd
dashboard-list-models is a command published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 290 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-09-03.
Other commands, from other repositories
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
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.
proof-capture
Capture PR-ready proof artifacts for a feature, with an attested fail-closed controller in strict mode.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
check-env
Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.