Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/test-engineer/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/test-engineer)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/test-engineer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/test-engineer.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 59 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00019 | $0.00516 |
| Opus 5 | $0.00010 | $0.00258 |
| Sonnet 5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade B, and why
test-engineer scanned grade B with 1 finding 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 8d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
Ensure quality through unit, integration, and E2E test coverage with risk-based test planning.
Core Responsibilities
- Analyze requirements for testability
- Write tests before implementation (TDD)
- Cover happy path and edge cases
- Test error conditions explicitly
- Verify performance requirements
- Document test scenarios
Testing Philosophy
- Prevention over Detection: Build quality in, not test it in
- Risk-Based: Focus on critical paths and high-impact areas
- Automated First: Manual testing only for exploratory needs
- Fast Feedback: Tests run quickly, fail clearly
Test Pyramid
- Unit Tests (70%): Fast, isolated, numerous
- Integration Tests (20%): Component interactions
- E2E Tests (10%): Critical user journeys
Examples
- "Create test suite for authentication"
- "Write integration tests for payment flow"
- "Build E2E tests for checkout process"
Guidelines
Test Quality Standards
- Coverage: >80% for unit, >70% for integration
- Naming: describe_what_when_expected pattern
- Isolation: No test dependencies
- Speed: Unit <100ms, integration <1s
- Deterministic: No flaky tests
Testing Patterns
- Arrange-Act-Assert: Clear test structure
- Given-When-Then: BDD scenarios
- Test Data Builders: Flexible test fixtures
- Mocking: Isolate dependencies
- Snapshot Testing: UI regression detection
Quality Requirements
- Tests included in same PR
- All tests must pass in CI
- Performance benchmarks included
- Test documentation updated
- No commented-out tests
Output Instructions
For report generation, see: @.claude/skills/test-engineer/template.md
Intelligence Queries
For accessing proven patterns and solutions, see: @.claude/skills/test-engineer/scripts/intelligence.sh
Skill Activation Announcement
MANDATORY — first line of every response after skill load:
Skill actief: test-engineer
No exceptions. This must appear before any other content.
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.
- 8d ago First seen · 78 lines · 19 tokens per session scan B 2d66278f05ef
test-engineer is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
three-tier-testing
Use when setting up test infrastructure, adding tests, reorganizing test directories, or reviewing test structure. Triggers include creating test files, discussing test strategy, separating unit from integration tests, or when tests need external services like databases or Docker.
Test Quality Inspector
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions.
Test Strategy
How to decide what to test at what level — the test pyramid, risk-based coverage, and matching test depth to change risk.
Android Testing
JUnit + Robolectric unit tests, Compose UI tests, screenshot tests, and Espresso for legacy views.
iOS Testing
XCTest unit tests, XCUITest UI tests, snapshot testing, and performance baselines for iOS apps.
Spring Test Pyramid
Unit, integration, slice, and E2E test patterns for Spring Boot applications.