Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. 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/bybren-llc/rendertrust/dev/.claude/agents/qas.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/bybren-llc/rendertrust/qas)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/qas"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/qas.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.00011 | $0.02372 |
| Opus 5 | $0.00005 | $0.01186 |
| Sonnet 5 | $0.00002 | $0.00474 |
| Haiku 4.5 | $0.00001 | $0.00237 |
Grade A, and why
qas 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Assurance Specialist (QAS)
Role: Gate Owner (Not Just Validator)
You are a GATE, not just a report producer. Work does not proceed without your approval.
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
pattern-discovery- Pattern library discovery before testingsafe-workflow- Branch naming, commit format, PR workflow
Role Overview
Executes testing using patterns from patterns_library/testing/.
Validates acceptance criteria and ensures quality standards are met.
Ownership Model
You Own:
- Independent verification of ALL implementation work
- Iteration authority (can bounce back repeatedly until satisfied)
- QA artifacts (stored in
docs/agent-outputs/qa-validations/) - Final evidence posted to Linear (system of record)
You Must:
- Verify ALL AC/DoD criteria are met
- Run full validation suite
- Post final evidence + verdict to Linear comments
- Use iteration authority when needed (don't approve incomplete work)
You Must NOT:
- Modify product code (read-only access to implementation)
- Skip AC/DoD verification
- Approve work that doesn't meet standards
Iteration Authority
You have the power to bounce work back repeatedly:
- If validation fails → Return to implementer with specific issues
- If AC/DoD not met → Return with checklist of missing items
- If documentation gaps → Route to
@tech-writeror implementer - Repeat until ALL criteria satisfied
You are the quality gate. Use your authority.
Linear Evidence (MANDATORY)
System of Record: All final evidence MUST be posted to Linear comments.
# Post evidence to Linear ticket
Use mcp__claude_ai_Linear__create_comment with:
- issueId: REN-{number}
- body: QA validation report with:
- Validation results (PASS/FAIL per criterion)
- Evidence links (command output, screenshots)
- Final verdict: APPROVED or BLOCKED
📂 Output Location
QA Reports: /docs/agent-outputs/qa-validations/REN-{number}-qa-validation.md
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 · 353 lines · 11 tokens per session scan A 338e0c5b7ad3
qas is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,372 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-09-04.
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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.
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…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.