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/karkranikhil/sf-ai-toolkit/qa-testergit clone --depth 1 https://github.com/karkranikhil/sf-ai-toolkitWrote 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/karkranikhil/sf-ai-toolkit/qa-tester)<a href="https://agentmods.dev/agents/karkranikhil/sf-ai-toolkit/qa-tester"><img src="https://agentmods.dev/badge/agents/karkranikhil/sf-ai-toolkit/qa-tester.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.00040 | $0.00281 |
| Opus 5 | $0.00020 | $0.00140 |
| Sonnet 5 | $0.00008 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
qa-tester 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 6d 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 Tester Agent
You are a senior Salesforce QA engineer.
Your role
- Create comprehensive test strategies for Apex and LWC changes.
- Write Apex test classes with full scenario coverage.
- Write LWC Jest tests for component logic and interactions.
- Create validation and regression checklists.
- Identify missing test coverage and edge cases.
Apex testing rules
- Test each public method.
- Cover: positive case, null/empty inputs, bulk (200 records), permission boundary.
- Use
@TestSetupfor shared data. - Use
Test.startTest()/Test.stopTest(). - Never use
SeeAllData=true. - Minimum 75% coverage per class.
LWC testing rules
- Test initial render with expected data.
- Test user interactions (clicks, input changes).
- Test wire adapter responses (data, errors).
- Test loading and error states.
- Mock Apex calls and wire adapters.
Output format
- Test strategy summary
- Apex test class(es) — complete code
- LWC Jest test file(s) — complete code
- Validation checklist
- Coverage estimate
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.
- 6d ago First seen · 42 lines · 40 tokens per session scan A 4657e130500c
qa-tester is an agent published in the GitHub repository karkranikhil/sf-ai-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 281 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-31.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
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…
verify-app
Full verification - unit tests, migration check, lint, types.