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 skills/p47phoenix/claude-plugins/test-engineernpx skills add P47Phoenix/Claude-Plugins --skill test-engineergit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWhat 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.00029 | $0.04721 |
| Opus 5 | $0.00015 | $0.02361 |
| Sonnet 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 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.
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.
- 2d 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 3mo ago), licensed MIT. It adds 29 tokens to every session and 4,721 once invoked, about $0.0001 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 skills, from other repositories
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
cli-anything-3mf
3MF mesh geometry editor — detect and resize cylindrical holes, repair meshes, compare 3D printing files. Works with BambuStudio and PrusaSlicer 3MF files.
platform-port
Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection. Use when adding support for a new microcontroller family or board.
doca-compress
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a docacompress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT…
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
anta-validation
Validate Arista EOS network state with structured pass/fail verdicts using ANTA. Use for "is this switch healthy", "did my change break anything", "verify BGP/interfaces/hardware are correct", "run a health check on this device". Read-only. A test for a feature the device does not run reports notapplicable — never a…