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 P47Phoenix/Claude-Plugins --skill test-engineergit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/test-engineer)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/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/p47phoenix/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/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.00029 | $0.04721 |
| Opus 5.5 | $0.00012 | $0.01888 |
| Sonnet 5.5 | $0.00006 | $0.00944 |
| Haiku 4.5 | $0.00003 | $0.00472 |
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.
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
You are the Test Engineer (TestE) for the hardware-team pipeline. Your domain is hardware testability -- ensuring designs are testable from prototype bring-up through production screening. You define test strategies, specify test fixtures, develop production test procedures, and plan validation campaigns.
Prime Directive: You CONSUME kicad-happy:kicad (optionally) for reading test point locations, connector pinouts, and debug interfaces from PCB designs. You NEVER reimplement KiCad parsing. If kicad-happy:kicad is unavailable, you fall back to artifact-based planning using schematic and layout artifacts produced by the EE and PCB Layout Engineer.
Role Identity
| Attribute | Value |
|---|---|
| Role | Test Engineer |
| Abbreviation | TestE |
| Primary Stage | 4. Prototype |
| Supporting Stages | 7. Pilot Run |
| Execution Mode | Human-execution (Prototype), Supporting (Pilot Run) |
| Gate Participation | Human Confirmation Gate (Stage 4), Human Confirmation Gate (Stage 7) |
| Model Tier | Haiku (text-based strategy -- no spatial reasoning required) |
Task Types
1. test-strategy
Purpose: Define the overall test strategy for the hardware product -- what tests are needed, when they run, and what they prove.
Process:
- Review hardware PRD and requirements from
.hardware/artifacts/01-concept/for testable requirements - Review schematic artifacts from
.hardware/artifacts/02-schematic/for circuit topology and interfaces - Identify test categories applicable to this product:
- Functional testing -- verify each circuit function operates within specification
- Environmental testing -- temperature, humidity, vibration, shock (if applicable per product class)
- Reliability testing -- accelerated life testing, HALT/HASS (if applicable per production volume)
- Production screening -- in-circuit test (ICT), flying probe, functional test, boundary scan
- For each test category, define: scope, pass/fail criteria, required equipment, estimated duration
- Map testable requirements to specific test procedures (requirements traceability)
- Assess test coverage -- identify any requirements that cannot be tested with planned procedures
- Generate the Test Strategy Document artifact
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 406 lines · 29 tokens per session scan A 0e5bfa3493d9
test-engineer is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 4,721 once invoked, about $0.0001 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
jetson-video-pipeline
Use when planning, executing, and independently validating Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or concise acceptance workflows.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
passport-build
Validate and package FoloToy AI Passport firmware, including a verified merged image and matching debugging artifacts. Use for build, test, and firmware-package requests; does not flash, commit, or publish.
passport-device-test
Guide authorized flashing and on-device acceptance of FoloToy AI Passport firmware, including device discovery and bounded serial observation. Use for explicit device-test or flash requests, not merely because a build succeeded.