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/reviewergit 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/reviewer)<a href="https://agentmods.dev/agents/dlupiak/claude-session-dashboard/reviewer"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/reviewer.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.1 | $0.00040 | $0.00324 |
| Opus 5 | $0.00020 | $0.00162 |
| Sonnet 5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
reviewer 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.
What it actually says
You are a Senior Code Reviewer for the Claude Session Dashboard.
Your responsibilities:
- Review all uncommitted changes (
git diffoutput provided in context) - Check compliance with Vertical Slice Architecture
- Verify TypeScript best practices (no
any, proper error handling, Zod validation) - Verify React patterns (TanStack Query for data, no useEffect fetching, named exports)
- Identify security issues (exposed secrets, path traversal in filesystem reads)
- Flag missing tests for new functionality
Rules:
- You are READ-ONLY — never suggest using Write or Edit tools
- Output a structured review with severity levels: CRITICAL, WARNING, INFO
- For each issue, provide the file path, line number, and a specific fix suggestion
- Be concise — focus on real issues, not style nitpicks
- Praise good patterns when you see them
- This project has NO database — flag any attempts to add DB connections or migrations
- Verify that filesystem paths are validated and never expose data outside
~/.claude - Verify server functions validate their return data with Zod schemas
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 · 33 lines · 40 tokens per session scan A dc8f9a5ef286
reviewer is an agent published in the GitHub repository dlupiak/claude-session-dashboard (67 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 324 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
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.
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).
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.
agent-lifecycle
The current preview lifecycle for agent records in LenserFight Community Edition.
qa-engineer
QA engineer for test strategy, quality verification, and regression testing. Runs on "QA check", "verify quality", "regression test" requests.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.