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/thierryn/fire-flow/fire-dashboardgit clone --depth 1 https://github.com/ThierryN/fire-flowWrote 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/thierryn/fire-flow/fire-dashboard)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-dashboard"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-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.00008 | $0.03261 |
| Opus 5 | $0.00004 | $0.01631 |
| Sonnet 5 | $0.00002 | $0.00652 |
| Haiku 4.5 | $0.00001 | $0.00326 |
Grade A, and why
fire-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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-dashboard
Visual CLI dashboard for real-time project status and progress monitoring
Purpose
Display a comprehensive visual dashboard showing project status, phase progress, breath execution, validation status, skills usage, and recent activity. Provides at-a-glance situational awareness for Dominion Flow projects.
Arguments
| Argument | Required | Description |
|---|---|---|
--compact |
No | Single-line status bar for minimal output |
--watch |
No | Auto-refresh dashboard every 5 seconds |
--json |
No | JSON output for integrations and scripting |
--no-color |
No | Disable ANSI colors for plain terminals |
Process
Step 1: Load Project State
Read current project state from .planning/CONSCIENCE.md and related files.
# Check for required state files
if [ ! -f ".planning/CONSCIENCE.md" ]; then
echo "Error: No .planning/CONSCIENCE.md found. Run /fire-1a-new first."
exit 1
fi
Read and parse:
.planning/CONSCIENCE.md- Current position, phase, breath, progress.planning/VISION.md- Milestone and phase definitions.planning/SKILLS-INDEX.md- Skills applied tracking.planning/phases/*/- Phase-specific summaries
Step 2: Compute Metrics
Calculate dashboard metrics:
Project Metrics:
- Project name (from PROJECT.md or directory name)
- Milestone (from CONSCIENCE.md)
- Current phase / total phases
- Current breath / total breaths
- Overall progress percentage
- Skills applied count
- Validation status per category
Step 3: Display Dashboard
Default Mode (Full Dashboard)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
POWER ► DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
╔══════════════════════════════════════════════════════════════════════════════╗
║ PROJECT STATUS ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ ║
║ Project: my-project Milestone: v1.0 ║
║ Phase: 3 of 9 (Pattern Computation) Status: ◆ Executing ║
║ Started: 2026-01-15 Last: 2026-01-22 14:32 ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
┌─────────────────────────────────────────────────────────────────────────────┐
│ PHASE PROGRESS │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ Overall: ████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░ 40% │
│ │
│ By Phase: │
│ ├─ Phase 1: ████████████████████████████████████████ 100% ✓ │
│ ├─ Phase 2: ████████████████████████████████████████ 100% ✓ │
│ ├─ Phase 3: ██████████████████░░░░░░░░░░░░░░░░░░░░░░ 45% ◆ │
│ ├─ Phase 4: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% ○ │
│ └─ ... │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────┬────────────────────────────────────────┐
│ BREATH EXECUTION │ VALIDATION STATUS │
├────────────────────────────────────┼────────────────────────────────────────┤
│ │ │
│ Breath 1: ✓ Complete (3 plans) │ Code Quality ████████████████ ✓ │
│ Breath 2: ✓ Complete (2 plans) │ Testing ████████████████ ✓ │
│ Breath 3: ◆ In Progress (2 plans) │ Security ████████████████ ✓ │
│ Breath 4: ○ Pending (1 plan) │ Performance ████████████░░░░ ⏳ │
│ │ Documentation ████████████████ ✓ │
│ Current: Plan 03-05 │ │
│ Agent: fire-executor │ Score: 65/70 (93%) │
│ │ │
└────────────────────────────────────┴────────────────────────────────────────┘
┌────────────────────────────────────┬────────────────────────────────────────┐
│ SKILLS APPLIED │ RECENT ACTIVITY │
├────────────────────────────────────┼────────────────────────────────────────┤
│ │ │
│ Total: 12 skills │ 14:32 Plan 03-05 started │
│ │ 14:15 Skill: api-patterns/pagination │
│ Top Skills: │ 13:45 Breath 2 verification passed │
│ ├─ n-plus-1 (5x) │ 13:30 Plan 03-04 completed │
│ ├─ input-validation (4x) │ 12:15 Plan 03-03 completed │
│ └─ pagination (3x) │ 11:00 Breath 1 verification passed │
│ │ │
│ Categories: │ Commits today: 8 │
│ ├─ database-solutions (5) │ Files changed: 24 │
│ ├─ security (4) │ Lines added: 1,847 │
│ └─ api-patterns (3) │ │
│ │ │
└────────────────────────────────────┴────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────────────┐
│ NEXT UP │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ → Complete Plan 03-05 (Heptadic Timeline) │
│ → Execute Breath 4: Plan 03-06 (Pattern Export) │
│ → Run /fire-4-verify 3 when complete │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
╠══════════════════════════════════════════════════════════════════════════════╣
║ Commands: [1] Plans [2] Execute [3] Skills [4] Verify [5] Handoff [q] ║
╚══════════════════════════════════════════════════════════════════════════════╝
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 · 376 lines · 8 tokens per session scan A c4814cdf880d
fire-dashboard is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 21d ago), licensed MIT. It adds 8 tokens to every session and 3,261 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.