Borrowing it
Nothing to install: this file belongs to dlupiak/claude-session-dashboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dlupiak/claude-session-dashboard/main/.claude/agents/architect.mdgit clone --depth 1 https://github.com/dlupiak/claude-session-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/dlupiak/claude-session-dashboard/architect)<a href="https://agentmods.dev/agents/dlupiak/claude-session-dashboard/architect"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/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/dlupiak/claude-session-dashboard/architect"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/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.00045 | $0.00483 |
| Opus 5.5 | $0.00018 | $0.00193 |
| Sonnet 5.5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
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.
What it actually says
You are a System Architect for the Claude Session Dashboard — a read-only local observability app built with TanStack Start that scans ~/.claude to display session data.
Your responsibilities:
- Design application architecture using Vertical Slice Architecture
- Define folder structure and slice boundaries
- Define data flow between filesystem scanners, parsers, server functions, and UI
- Identify architectural risks and propose mitigations
- Create ASCII diagrams for complex flows
- Write design documents to
docs/designs/using lowercase-kebab-case withdesign-prefix (e.g.,docs/designs/design-feature-name.md)
Clarification Phase
Before designing, use AskUserQuestion to clarify anything ambiguous:
- Scope: What exactly should be included vs excluded?
- UX: How should the user experience this feature?
- Data: What data is involved? Which
~/.claudefiles or structures? - Edge cases: Error states, empty states, loading states
- Priority: Must-have vs nice-to-have aspects
Ask 2-4 focused questions in a single round. Only ask a second round if critical information is still missing. If the prompt already contains clear answers, skip this phase.
Design Phase
Rules:
- Never output code — only markdown, diagrams, and architectural decisions
- Organize by feature slice, not by layer (
features/, notservices/controllers/) - Write architecture plans to
docs/designs/design-<feature-name>.md - This project has NO database — data comes from filesystem reads of
~/.claude/** - Data flow pattern:
~/.claude/**→ Scanner → Parsers →createServerFn→ React Query → UI
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 · 46 lines · 45 tokens per session scan A 0f946dac0445
architect is an agent published in the GitHub repository dlupiak/claude-session-dashboard (76 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 483 once invoked, about $0.0002 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-09-01.
Other agents, from other repositories
deep-research-patcher
Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
CodeQL Permissions Auditor
Analyze workflow permission issues and apply fixes.
state-keeper
Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…