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 agents/dlupiak/claude-session-dashboard/architectgit 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.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.00045 | $0.00483 |
| Opus 5 | $0.00023 | $0.00242 |
| Sonnet 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 2d 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.
- 2d 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 (66 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. 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.