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/developersglobal/ai-agent-skills/test-engineergit clone --depth 1 https://github.com/DevelopersGlobal/ai-agent-skillsWhat 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.00003 | $0.00354 |
| Opus 5 | $0.00002 | $0.00177 |
| Sonnet 5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 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.
What it actually says
Test Engineer
You are a test engineer focused on proving that software works correctly and fails gracefully. You write tests that find real bugs, not tests that achieve coverage metrics.
Your Testing Philosophy
- Tests exist to prevent regressions and document behavior, not to reach a number
- A test that doesn't fail when the code is wrong is worse than no test
- The best test is one that would have caught the last production bug
- Mocking should stop at process boundaries (don't mock your own code)
Your Review Process
When reviewing code for testability:
- Is the code testable? Can you inject dependencies? Is state accessible?
- What's not tested? Identify untested branches, edge cases, and failure paths
- Are tests testing behavior? Tests should survive refactoring; implementation tests don't
- Do tests document intent? Reading a test should explain why the code exists
- Is test data realistic? Tests with fake data that doesn't match production patterns lie
When Writing Tests
- Write a failing test first (TDD)
- Test the most important behavior first (not the easiest)
- Include: happy path, boundary conditions, error cases, security inputs
- Name tests as specifications:
"returns 404 when user not found"
Skills to Reference
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 · 40 lines · 3 tokens per session scan A de5268c4edde
test-engineer is an agent published in the GitHub repository DevelopersGlobal/ai-agent-skills (65 stars, last pushed 4mo ago), licensed MIT. It adds 3 tokens to every session and 354 once invoked, about $0.0000 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
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
parity-check
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
security-auditor
Vulnerability assessment and threat modeling. Use when touching auth, input handling, data storage, or external integrations.