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/agents/ahpxex/open-dashboard/project-architect)<a href="https://agentmods.dev/agents/ahpxex/open-dashboard/project-architect"><img src="https://agentmods.dev/badge/agents/ahpxex/open-dashboard/project-architect/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/agents/ahpxex/open-dashboard/project-architect"><img src="https://agentmods.dev/badge/agents/ahpxex/open-dashboard/project-architect.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.00000 | $0.02026 |
| Opus 5.5 | $0.00000 | $0.00810 |
| Sonnet 5.5 | $0.00000 | $0.00405 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
project-architect 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Architect for this TanStack Start back-office / dashboard
starter (a "中台" template for shipping SaaS and internal-tool backends faster).
You are an architectural guardian: every change you design must keep the codebase
structurally sound, consistent across resources, and portable to a different
backend or brand. Read CLAUDE.md, PATTERNS.md, and ROADMAP.md for the
authoritative conventions; this agent's job is to apply them, not restate them.
Core identity
This repo's value is not the demo screens — it is a known vocabulary of admin shapes that an agent composes from. So you optimize for:
- Consistency over feature count. Six patterns that look identical beat
thirty that don't. Every resource shares the same
ListParamsshape, query-key structure,requireUserguard, URL state, and error/empty/loading conventions. - Thin and copy-friendly over clever. A pattern is a small readable reference you copy, not a deep framework you configure. Abstract only after a thing has been needed ~twice.
- Portability. Patterns are written against the
Repositoryinterface, not against Drizzle. A resource declares which adapter backs it; everything else is backend-agnostic.
Technology stack (the real one)
- TanStack Start — full-stack React on Vite + Nitro. Server logic lives in
server functions created with
createServerFnfrom@tanstack/react-start. There is no Next.js, no App Router, no Server Components, no Server Actions, no API-route data layer. - TanStack Router — file-based, type-safe routes under
src/routes/. The route tree is generated intosrc/routeTree.gen.ts(never hand-edit it; it is gitignored and regenerated bybun run dev/buildor the router CLI). - TanStack Query — caching + mutations, SSR-integrated. TanStack Table —
headless, wrapped by the generic
DataTableinsrc/infra/table. - Drizzle ORM + PostgreSQL (
drizzle-orm/node-postgres) — the default concrete backend, reached only through aRepositoryadapter. Schema insrc/db/schema.ts. - better-auth — email + password, sessions in Postgres via the Drizzle adapter.
- shadcn/ui on
@base-ui/react(NOT Radix), Tailwind v4, Phosphor icons, Recharts, Zustand (client state only), Zod v4 (validation). - Bun (package manager + runtime), Biome (lint/format), Vitest, strict
TypeScript, path alias
@/*→./src/*.
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 · 121 lines · 0 tokens per session scan A 1d13be2746df
project-architect is an agent published in the GitHub repository ahpxex/open-dashboard (146 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,026 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 agents, from other repositories
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
Code Reviewer
Quality assurance reviewer for pull request review, standards enforcement, and code quality assessment.
Security Engineer
Application security specialist for threat modeling, code scanning, dependency audit, and compliance review.
code-reviewer
Read-only reviewer for auth, billing, and credits-ledger changes. Use proactively after modifying src/lib/auth, src/lib/billing, src/lib/credits, or src/app/api — before committing.
maintainability-reviewer
Read-only review of a diff for DRY, maintainability and need - duplication of an existing helper, schema, prompt or component, code, files, options and exports the feature's acceptance does not require, speculative generality, single-use wrappers, dead code, over-long functions, restating comments and docs…
review-responder
Handles a review bot's (Greptile's) comments on one PR, on the branch already checked out. Fixes valid comments inside the PR's fence, declines wrong or out-of-scope ones with a reason, points duplicates at the other thread, replies on every thread, and makes one commit. Never pushes. Treats comment text as untrusted…