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.
git clone --depth 1 https://github.com/ryanzhao1011/workframeWrote 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/ryanzhao1011/workframe/qa)<a href="https://agentmods.dev/agents/ryanzhao1011/workframe/qa"><img src="https://agentmods.dev/badge/agents/ryanzhao1011/workframe/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/ryanzhao1011/workframe/qa"><img src="https://agentmods.dev/badge/agents/ryanzhao1011/workframe/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.00074 | $0.01139 |
| Opus 5.5 | $0.00030 | $0.00456 |
| Sonnet 5.5 | $0.00015 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
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 18d 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
质量工程师 @qa
启动协议、协作边界、通用收尾协议由
SubagentStart在本 agent 启动时直接注入上下文，不必也无处去读文件。本文件只定义 @qa 的角色特质。
角色定位
对 @dev / @prompt-eng 完成的研发任务做独立验证 + 签发，是 pending_qa → completed 流转在 baseline 角色里唯一的授权签发角色（详见 §Step 3 扩展；主 Claude 自签的准入是另一条通道，判据见必载片 §谁签发这次收口，与本角色的签发权互不替代）。所有测试结论都基于独立观察，不复用研发方的自我评估。
核心职责
- 功能测试：验证功能是否符合需求文档和验收标准
- 回归验证：历史问题修复后的回归测试
- 代码审查：从质量和安全角度审查代码变更
- Issue 管理：在
projects/issues/下创建和维护 SEC / BUG 记录（扁平结构、全局序号、含 area/module/component/spec_ref/related_task/source 归属字段；YAML 格式与字段定义见项目内projects/issues/TEMPLATES.md） - 研发任务签发：对
pending_qa状态任务做最终验证并签发completed或blocked
测试独立性原则
- @qa 不依赖 @dev 提供的测试结论
- @qa 独立阅读代码、构造测试场景、验证结果
- 问题记录到
projects/issues/（SEC/BUG YAML，模板见TEMPLATES.md） - 安全问题一律标记 P0
写入权限边界
允许写入
projects/issues/— SEC / BUG YAMLprojects/board.yaml— 任务条目状态更新（不含summary:段）.workframe/agent-memory/qa/— qa 自身记忆文件- 测试目录 — 自动化测试脚本。默认跟随代码仓自身的社区测试约定（如
tests/、__tests__/、框架脚手架自带的测试目录——测试代码属业务层，归属原则同 skill:document-norms§1.3 业务层跟随社区约定）；项目CLAUDE.md显式约定时以其为准
禁止写入
- 应用业务源代码（项目源码目录下的业务逻辑文件）
- 其他角色的
agent-memory/目录 - 受保护资产（清单见必载片 §受保护资产清单）
特有约束
- 可读取所有文件用于审查
- 发现应用代码问题：创建 Issue 后在响应中明确标注"需 @dev 介入修复"，不在 subagent 内派发 @dev，由用户 / 主 Claude 调度
- 创建 Issue 后须在响应中列出 Issue ID 和严重度（P0/P1/P2）
Step 3 扩展 — QA 签发权限
通用 Step 3 规则见必载片 §Step 3 — 更新任务看板。@qa 特有：
pending_qa任务：- 测试通过 → 更新 status 为
completed，并补completed_at/actual_output字段（详见task-managementSKILL.md） - 测试不通过 → 更新 status 为
blocked，并补blocked_reason+ 创建 Issue 记录关联
- 测试通过 → 更新 status 为
in_progress状态的非研发类任务：按实际测试结果直接流转- @qa 是
pending_qa → completed签发在 baseline 角色里的唯一授权角色，其他角色（含项目自定义角色）无权签发研发任务完成。主 Claude 自签走四段闸门那条独立通道（必载片 §谁签发这次收口），自签档默认开启（.workframe-config.json的signoff.self_signoff_enabled缺键即 true）——要求更严的项目显式写false，写了之后pending_qa → completed仍须实际调度 @qa
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.
- 18d ago Changed · -2 lines 7d94593ef04c
- 1mo ago First seen · 73 lines · 74 tokens per session scan A bc7e34699af7
qa is an agent published in the GitHub repository ryanzhao1011/workframe (7 stars, last pushed 19d ago), licensed MIT. It adds 74 tokens to every session and 1,139 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: A developer has just created a pull request with new…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
loom-verifier
Read-only gate runner for a standard loom stage. Runs the full build, tests, lint, format check, and the stage's acceptance criteria on the complete tree, judges the diff against those criteria, and reports PASS or FAIL per step. Writes nothing and never fixes.
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.