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 skills add Aizaz-Noor/Agent-Startup-Skills --skill test-engineergit clone --depth 1 https://github.com/Aizaz-Noor/Agent-Startup-SkillsWrote 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/skills/aizaz-noor/agent-startup-skills/test-engineer)<a href="https://agentmods.dev/skills/aizaz-noor/agent-startup-skills/test-engineer"><img src="https://agentmods.dev/badge/skills/aizaz-noor/agent-startup-skills/test-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aizaz-noor/agent-startup-skills/test-engineer"><img src="https://agentmods.dev/badge/skills/aizaz-noor/agent-startup-skills/test-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00463 |
| Opus 5.5 | $0.00020 | $0.00185 |
| Sonnet 5.5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
test-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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-engineer — 100% identical, 0 lines differ
What it actually says
Test Engineer — Quality Assurance Agent
Purpose
Ensure the codebase works correctly by writing automated tests and identifying edge cases that the Coder may have missed.
When to Use
- After the codebase is implemented
- When the user asks for test coverage
- Before security audit (Phase 7 of SaaS Accelerator)
Process
Step 1: Test Strategy
Define what to test:
- Unit Tests: Individual functions and utilities
- Integration Tests: API endpoints (request → response)
- Edge Cases: Empty inputs, boundary values, unauthorized access
Step 2: Unit Tests
For each business logic function:
- Test the happy path (expected inputs → expected outputs)
- Test with invalid inputs (null, empty, wrong type)
- Test boundary values (min/max limits)
Step 3: API Integration Tests
For each API endpoint:
- Test successful request (correct status code and response body)
- Test with missing required fields (expect 400)
- Test without authentication on protected routes (expect 401)
- Test with invalid data types (expect 422)
Step 4: Edge Case Identification
Systematically check:
- What happens with an empty database?
- What happens with duplicate entries?
- What happens with very long strings?
- What happens with concurrent requests?
- What happens when an external service is unavailable?
Step 5: Test Runner Configuration
Generate the test runner config file (e.g., jest.config.js, pytest.ini)
and a test run command in package.json scripts.
Output
- Test files organized in a
tests/directory testing_plan.mdwith coverage summary- Manual test checklist for things that cannot be automated
Exit Criteria
- Every API endpoint has at least one happy-path test
- Every core business logic function has unit tests
- At least 5 edge cases are explicitly tested
- Test runner is configured and documented
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.
- 1mo ago First seen · 65 lines · 49 tokens per session scan A a225c549b6a8
test-engineer is a skill published in the GitHub repository Aizaz-Noor/Agent-Startup-Skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 463 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
unit-test-architect
Comprehensive unit testing patterns, mock/stub usages, and edge-case scenario coverage. / TR: Kapsamlı birim (unit) testleri, mock/stub kullanımları ve edge-case (uç durum) senaryoları yazma becerisi.
test-orchestrator
QA & testing orchestrator managing unit tests, E2E user scenarios, load testing, and performance benchmarks. / TR: Kapsamlı test stratejileri, birim testleri (unit), uçtan uca testler (E2E), performans ve yük testlerini yöneten ana orkestratör.
testing-master
Automated test strategies, unit testing, and E2E testing guidelines. / TR: Test stratejileri, birim testleri (unit test) ve e2e testler yazmak için yetenek.
agent-evals
Build automated evaluation suites for AI agents using golden datasets, rubrics, and regression gates. Use when shipping agent features, validating prompt changes, or gating deployments on quality.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…