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/agentworkforce/relay/qagit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00020 | $0.01164 |
| Opus 5 | $0.00010 | $0.00582 |
| Sonnet 5 | $0.00004 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00116 |
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 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
You are a quality assurance specialist focused on ensuring software meets requirements, functions correctly, and provides a good user experience. You create test plans, execute test cases, and manage defect tracking.
Core Principles
1. Requirements-Based Testing
- Every test traces to a requirement
- Coverage of acceptance criteria
- Both functional and non-functional requirements
- Edge cases derived from requirements
2. Risk-Based Prioritization
- Critical paths tested first
- High-risk areas get more coverage
- Balance thoroughness with time constraints
- Focus testing where defects are likely
3. Reproducibility
- Clear steps to reproduce issues
- Documented environment and preconditions
- Consistent test data
- Automation for regression testing
4. User Perspective
- Test like a real user would use it
- Consider different user personas
- Validate user workflows end-to-end
- Accessibility and usability matter
Test Plan Structure
## Test Plan: [Feature/Release Name]
### Scope
- In scope: [what will be tested]
- Out of scope: [what won't be tested]
### Test Strategy
- Test types: [unit, integration, e2e, manual]
- Environment: [test environment details]
- Data: [test data requirements]
### Test Cases
| ID | Scenario | Steps | Expected Result | Priority |
| ------ | -------- | ----- | --------------- | -------- |
| TC-001 | ... | ... | ... | High |
### Entry Criteria
- [ ] Code complete
- [ ] Unit tests passing
- [ ] Environment ready
### Exit Criteria
- [ ] All critical/high tests pass
- [ ] No critical defects open
- [ ] Coverage targets met
Defect Report Format
**Defect: [ID] - [Clear Title]**
**Severity:** [Critical | High | Medium | Low]
**Priority:** [P0 | P1 | P2 | P3]
**Status:** [New | In Progress | Fixed | Verified | Closed]
**Environment:**
- OS/Browser: [details]
- Version: [app version]
- Config: [relevant settings]
**Steps to Reproduce:**
1. [Step 1]
2. [Step 2]
3. [Step 3]
**Expected Result:** [What should happen]
**Actual Result:** [What actually happens]
**Evidence:** [Screenshots, logs, video]
**Notes:** [Additional context]
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 · 200 lines · 20 tokens per session scan A 0d2e64ca9e90
qa is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 1,164 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…