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/aizhangdeshuai-cmd/hlskills/test-engineergit clone --depth 1 https://github.com/aizhangdeshuai-cmd/hlskillsWrote 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/agents/aizhangdeshuai-cmd/hlskills/test-engineer)<a href="https://agentmods.dev/agents/aizhangdeshuai-cmd/hlskills/test-engineer"><img src="https://agentmods.dev/badge/agents/aizhangdeshuai-cmd/hlskills/test-engineer.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.01594 |
| Opus 5 | $0.00023 | $0.00797 |
| Sonnet 5 | $0.00009 | $0.00319 |
| Haiku 4.5 | $0.00005 | $0.00159 |
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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 123 lines · 45 tokens per session scan A b8958a564b8e
test-engineer is an agent published in the GitHub repository aizhangdeshuai-cmd/hlskills (2 stars, last pushed 20d ago), with no licence file. It adds 45 tokens to every session and 1,594 once invoked, about $0.0002 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 agents, from other repositories
qa-engineer
QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.
Test Engineer
Senior SDET who owns end-to-end quality — test strategy, TDD coaching, coverage policy, TestContainers/E2E execution, and bug triage.
harness-implementer
Implements a single claude-harness feature end-to-end in an isolated context - acceptance tests first (ATDD), implementation, verification, checkpoint (commit/push/PR via gh), optional merge. Spawned by the /claude-harness:flow skill with a structured feature prompt; not intended for ad-hoc use.
benchmark-manager
Agent "benchmark-manager" from revfactory/harness-100, covering benchmark manager — benchmark administrator, core role, principle, workspace/04benchmarkresults.md save as file and team as.
backend-phase-6
You are the Controller Layer Agent. You build thin HTTP controllers using test-driven development. You write E2E tests FIRST with Supertest, then implement controllers that validate input and delegate to services. Controllers are the HTTP boundary — they deal with requests, responses, and status codes.
test-writer
Writes failing test scripts using Playwright CLI to verify expected behavior before implementation. Use after plan approval to establish the Red phase of TDD.