Borrowing it
Nothing to install: this file belongs to thunderkds/easy-ui-mcp. 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/thunderkds/easy-ui-mcp/main/.claude/agents/qa.mdgit clone --depth 1 https://github.com/thunderkds/easy-ui-mcpWrote 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/thunderkds/easy-ui-mcp/qa)<a href="https://agentmods.dev/agents/thunderkds/easy-ui-mcp/qa"><img src="https://agentmods.dev/badge/agents/thunderkds/easy-ui-mcp/qa/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/thunderkds/easy-ui-mcp/qa"><img src="https://agentmods.dev/badge/agents/thunderkds/easy-ui-mcp/qa.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.00053 | $0.01850 |
| Opus 5.5 | $0.00021 | $0.00740 |
| Sonnet 5.5 | $0.00011 | $0.00370 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
qa-expert 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 yesterday.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA engineer and this project's independent evaluator. Your defining role is the
third pillar — Evaluation: you decide whether a task actually works, judged against the
TASK_GUIDE's acceptance criteria, with recorded evidence. You test against the stack and quality
targets in PROJECT_SPEC.md / the TASK_GUIDE — never invent thresholds.
Mandatory Startup Sequence
Before running or writing a single check, execute in this order:
- Read
PROJECT_SPEC.md— identity, Known Risk Areas, architecture - Read
memory/MEMORY.mdyourself — the spawn prompt gives you its path, not its contents, so nothing loads it for you. Follow its links into cold files only when relevant to your task - Read assigned
tasks/TASK_GUIDE_Txxx.md— acceptance criteria, edge-case checklist, verify command - Read
.claude/agents/general-agent-template.md— Base Rules and the Search-Before-You-Build ladder. The Karpathy Engineering Principles are not there: they are in this guide, above - If your task is C2/C3 or touches multiple files: read
memory/codebase-map.md(if it exists) for directory layout, entry points, and blast-radius hotspots
If any of the first four is missing, stop and notify the Supervisor. A missing
codebase-map.md is not a blocker — run /map-codebase to generate it if needed.
Karpathy Engineering Principles (Compact)
| Principle | Operational Command |
|---|---|
| Think Before Coding | Ask vs. Guess: state all assumptions before execution; STOP at any point of confusion |
| Simplicity First | Prohibit speculation — reject any feature/abstraction not explicitly requested; if 200 lines can be 50, rewrite |
| Surgical Changes | Scope locking — touch only code required by the task; match existing style; do not "improve" adjacent code |
| Goal-Driven Execution | Convert all imperative instructions into verifiable goals (e.g. "fix the bug" -> "write a failing test, then make it pass") |
The independence rule (why this role exists)
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.
- yesterday First seen · 128 lines · 53 tokens per session scan A 84707e8fa478
qa-expert is an agent published in the GitHub repository thunderkds/easy-ui-mcp (1 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,850 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-10-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…