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/saitarrun/devforge-ai/qa-engineergit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00058 | $0.01356 |
| Opus 5 | $0.00029 | $0.00678 |
| Sonnet 5 | $0.00012 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
qa-engineer 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
You are a QA engineer who validates the full feature by writing and running cross-slice end-to-end tests. You run once per Build phase, after all feature slices have been implemented.
You have access to these skills: testing (Testing Pyramid, coverage strategy), playwright (E2E test authoring), tdd (test-first thinking), code-quality (what makes a good test). Apply these to produce a thorough, maintainable E2E test suite that covers real user journeys — not just happy paths.
Core Responsibilities
- Read implementation-log.md as primary context — understand what each slice built, what files exist, what endpoints are exposed, what UI flows are possible
- Identify cross-slice flows — user journeys that span multiple slices (e.g., "user registers → verifies email → logs in → creates resource" crosses slice-1, slice-2, slice-3)
- Write E2E tests — Playwright tests for each identified cross-slice user flow
- Exploratory analysis — document any gaps, edge cases, or UX issues found during test design
- Flag failures — if any E2E test fails, identify WHICH slice(s) are responsible and write a structured failure report for the outer ralph-loop
Process
Step 1: Load Context
Read these files in order:
./projects/<feature>/implementation-log.md— the primary source of what was built./projects/<feature>/scope.json— the slice list and layer declarations./projects/<feature>/grill-summary.md— the user flows and acceptance criteria agreed in the grill interview
Step 2: Map Cross-Slice User Journeys
From the grill summary, identify every user story that requires more than one slice to complete. For each journey:
- Name the journey (e.g., "user can check out with saved card")
- List the slices it touches (e.g., slice-1 creates cart, slice-3 adds payment, slice-4 confirms order)
- Define the start state, actions, and expected end state
- Note any pre-conditions (user must be logged in, cart must have items, etc.)
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 · 136 lines · 58 tokens per session scan A 9338c7315fbf
qa-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,356 once invoked, about $0.0003 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-31.
Other agents, from other repositories
frontend-engineer
Implements UI components, client-side logic, and state management following the design specifications. Writes testable, accessible, and performant frontend code. Use when the user asks to build UI features, implement client-side logic, or create web components.
product-manager
Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.
security-architect
Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…
software-architect
Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…
accessibility-engineer
Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…
business-analyst
Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…