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/nguyenthienthanh/aura-frog/dashboardgit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/dashboard)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/dashboard"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/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.00000 | $0.01119 |
| Opus 5 | $0.00000 | $0.00560 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aura-frog:dashboard
CLI status display — terse one-screen view of plan tree, active task, conflicts, freezes, token budget, recent decisions.
Usage
/aura-frog:dashboard # static one-shot snapshot (default)
/aura-frog:dashboard --live # live refresh every 5s (until Ctrl-C)
/aura-frog:dashboard --json # machine-readable JSON for automation
/aura-frog:dashboard --section <name> # only one section: plan|active|conflicts|memory|mcp|preflight
Sections
sections[6]{name,what_it_shows}:
plan,"T0-T4 tree summary: counts per tier, status histogram, deviation_score across active path"
active,"Active task + ancestors + frozen count + recent run-state.json"
conflicts,"Open conflicts (unresolved CONFLICT-NNNNN), stale frozen (>24h), arbitration history tail"
memory,"permanent_memory.md size + last Epic distillation timestamp + Tentative-section count"
mcp,"per-server enable + 24h call count + blocked count + rate-limit status"
preflight,"session bypass count + last block reason + linter version"
Static output (default)
🐸 Aura Frog — Dashboard
─────────────────────────────────────────────────────────────
Plan tree (5 nodes · 8/8 invariants ✓)
▶ INIT-001 ✓ FEAT-A ✓ FEAT-B ✓ FEAT-C ✓ FEAT-D ▶ FEAT-E
Active path: MISSION → INIT-001 → FEAT-E → STORY-0050 → TASK-00200
Tier counts: T0=1, T1=1, T2=5, T3=12, T4=47
Active task (TASK-00200) — Phase 3 (GREEN)
Status: active · revision 2 · deviation 0.18 · replan budget 2/3
Recent: 12 trace events · 0 hallucinations flagged · 1 file_write
Ready queue: 4 · Frozen: 0 · Blocked: 0
Conflicts: 0 open · 0 stale (>24h)
Memory: permanent_memory.md 4 Epics · 2,840 tokens / 8,000 cap · 0 Tentative
MCP: 6 servers enabled · 87 calls today · 0 blocked
Pre-flight: 0 bypasses this session · last block: never
Protocol — static (default)
- Read
.claude/plans/active.jsonfor active path - Run
bash scripts/plans/render-plan-tree.shfor tier counts (parsed, not rendered tree) - Read latest run-state from
.claude/logs/runs/<latest>/run-state.json - Read open conflicts from
.claude/plans/conflicts.jsonl(latest per conflict_id, filter resolution: null) - Read
.claude/memory/permanent_memory.mdfor size + Epic count - Read
<security-dir>/mcp-audit.jsonltail (last 24h) for MCP stats (seehooks/lib/security-dir.cjs) - Read
.claude/logs/.preflight-bypass-countfor session bypass count - Project all into TOON via
scripts/json-to-toon.cjs --schema genericper section - Render to stdout
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 · 92 lines · 0 tokens per session scan A 3bdcc5be70be
dashboard is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,119 tokens. 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-30.
Other commands, from other repositories
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
create_plan
Create detailed implementation plans through interactive research and iteration.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
research_codebase
Document codebase as-is with thoughts directory for historical context.
resume_handoff
Resume work from handoff document with context analysis and validation.
create_handoff
Create handoff document for transferring work to another session.