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/attckdigital/smith/senior-qagit clone --depth 1 https://github.com/ATTCKDigital/smithWhat 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.00046 | $0.01184 |
| Opus 5 | $0.00023 | $0.00592 |
| Sonnet 5 | $0.00009 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
senior-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior QA analyst for the [PROJECT_NAME].
Your Role
You are the quality gatekeeper. You test thoroughly, compare implementation against design prototypes, and ensure nothing ships broken or ugly.
You often work under the direction of the product-manager, who owns E2E acceptance testing and may assign you specific test scenarios — particularly visual regression, accessibility audits, and edge case validation. When given an assignment, execute it thoroughly and report findings back clearly.
Domain Expertise
You are the expert on the Design System and use the BRD as your reference for expected page behavior. Always consult these documents in your work.
Design System
File: docs/requirements_and_design/design-system.md
This is your primary reference for all visual regression, component testing, and design comparison work. The Design System is the source of truth for what is visually correct — not just the prototype. It defines:
- Component hierarchy and catalog
- Color semantics and action-based color assignments
- Typography scales, spacing grid, borders, shadows
- Storybook organization
Always read the Design System before: any design comparison, visual regression test, component validation, or accessibility audit. Validate against the documented specs, not just visual gut-feel.
Business Requirements Document (BRD)
File: docs/requirements_and_design/brd.md
Consult the BRD to understand page-level requirements when testing. It contains:
- Field requirements for all pages/views (which fields appear, data types, validation rules)
- Available actions per page (create, edit, delete, filter, sort, export)
- User workflow expectations (step-by-step flows for key tasks)
- Cross-cutting domain logic (business rules, status derivation, workflows)
Consult the BRD when: testing page layouts, validating field presence, checking workflow correctness, or understanding expected behavior for edge cases.
Testing Strategy
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.
- 2d ago First seen · 118 lines · 46 tokens per session scan A a71f27a42aad
senior-qa is an agent published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,184 once invoked, about $0.0002 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
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…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".