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/ahpxex/open-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/ahpxex/open-dashboard/port)<a href="https://agentmods.dev/commands/ahpxex/open-dashboard/port"><img src="https://agentmods.dev/badge/commands/ahpxex/open-dashboard/port/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/ahpxex/open-dashboard/port"><img src="https://agentmods.dev/badge/commands/ahpxex/open-dashboard/port.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.00024 | $0.00239 |
| Opus 5.5 | $0.00010 | $0.00096 |
| Sonnet 5.5 | $0.00005 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
port 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 1mo 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
Port this admin template into a new product per PORTING.md.
Product brief: $ARGUMENTS
Work in order, using the matching skills and verifying (typecheck/check/
test) after each step:
- scaffold-dashboard — stand up the clean platform base in a new project. It ships demo-free + gallery-free and runs zero-config, so you add what the brief needs rather than stripping a demo.
- rebrand — set name/logo/description/theme in
src/config/app.ts. - Pick the data source for each entity (Drizzle / REST / GraphQL) via add-backend.
- Add the resources and page shapes the brief needs via add-backend and the add-component catalogue (detail, master-detail, card-list, chart-page, kanban, …).
Confirm the plan with the user before running migrations.
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.
- 1mo ago First seen · 24 lines · 24 tokens per session scan A 9fb5d6c278bc
port is a command published in the GitHub repository ahpxex/open-dashboard (146 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 239 once invoked, about $0.0001 per session on Opus 5.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
add
Add addons or a workspace package to the current Better-T-Stack project. Plans the change, confirms it with you, then applies it.
shadcn-form-guide
This guide demonstrates proper ShadCN form implementation using @tanstack/react-form with the October 2025 component suite (Field, InputGroup, etc.).
kill
run this command in the terminal.
dark-mode
You are a rigorous UI accessibility and design reviewer for React apps using Tailwind CSS v4 and Shadcn UI. You must.
review-as-tanner
Pretend you are the creator of Tanstack Start, Tanner Linsley, now review the following page structure, performance, data loading, etc to provide actionable feedback and suggestions. Create a file called REVIEW.md and log them all in an MD file so that I can make sure that we know everything has been reviewed and…
build-feature
Build a feature with the harness sub-agents fanned out in parallel — orient, fix the contract, parallel build lanes on disjoint files, parallel verification, synthesis.