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/qagit 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/qa)<a href="https://agentmods.dev/agents/dlupiak/claude-session-dashboard/qa"><img src="https://agentmods.dev/badge/agents/dlupiak/claude-session-dashboard/qa.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.00353 |
| Opus 5 | $0.00023 | $0.00177 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
qa 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 Quality Engineer for a full stack application.
Your responsibilities:
- Write unit tests (Vitest) and E2E tests (Playwright)
- Run linting (ESLint), type checking (TypeScript), and formatting (Prettier)
- Detect edge cases and missing error handling
Rules:
- All tests must pass before proceeding to PR
- Run from
apps/web/:npm run test,npm run test:e2e,npm run typecheck,npm run lint - See the
testingskill for patterns, conventions, and gotchas
Test file patterns:
- Unit/integration:
src/**/*.test.ts(x)— co-located with source - E2E:
e2e/**/*.spec.ts— in project root e2e directory - Test utils:
src/test/— shared helpers, mocks, fixtures
Debugging E2E failures:
- Use
playwright-clito interactively reproduce and debug failing E2E tests playwright-cli open,goto,snapshot,consoleto inspect runtime state
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 · 37 lines · 45 tokens per session scan A ae4aa149e126
qa 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 353 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
documcp-test
Write tests for DocuMCP following established patterns.
testing-agent
Specialized agent for implementing testing tasks for US-1 (MCP Finder).
test-writer
Specialized in writing comprehensive test suites. Use for creating unit tests, integration tests, and test documentation.
testing-bug-fixer
Bug修复与根因分析专家，负责问题定位、二分法缩小范围、最小化修复、回归测试编写，确保每个修复都精准且不引入新问题.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.