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 arozumenko/sdlc-skills --skill test-automation-implementationgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/test-automation-implementation)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/test-automation-implementation"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/test-automation-implementation/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/arozumenko/sdlc-skills/test-automation-implementation"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/test-automation-implementation.svg" alt="Reviewed on agentmods" width="80" 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 Tool Misuse · line 65 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00082 | $0.09641 |
| Opus 5 | $0.00041 | $0.04820 |
| Sonnet 5 | $0.00016 | $0.01928 |
| Haiku 4.5 | $0.00008 | $0.00964 |
Grade A, and why
test-automation-implementation 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 10d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation Implementation
The engineer slot's own skill — the full IC contract, preloaded by
test-automation-engineer. Pipeline philosophy, orchestration, and the batch
mechanics live in the
test-automation-workflow skill (load
on demand); this skill is what the engineer needs at hand on every dispatch.
Engineer slot contract
This skill IS the build slot in the test-automation pipeline. When dispatched — by an orchestrator like test-automation-lead, or standalone for "automate the case at <path>" — role, context, parameters, and return shape are fixed here so dispatch prompts don't have to inline them.
Role. Take a test case — from the TMS or tasks/<suite>/TC-*.md; the case is never edited by TA — plus execution evidence when it exists, write the spec (and any required page-object / fixture changes) carrying a coverage declaration (§ Coverage declaration below), and run it green once locally — determinism is proven by the orchestrator's batch hardening gate, not by repeated local runs; hand back a PR-ready diff plus a Run Report.
Two build modes (the dispatch names the route):
- Evidence-backed — route
manual-qa-verified, orneeds-executionafter the lead obtained a PASS test-runner record. The case has been executed live by the manual-qa side; build from the case plus its run record (reports/RUN-*.md), no re-execution — cite the run id as execution provenance in the Run Report. Evidence missing for a case on this route → return to the lead; never silently self-execute when policy says manual-qa (.agents/testing.md§ Execution provider). - Combined — route
combined(providerself). No prior execution exists and none is required first: the first green run of your automated test against the real system IS the case's first execution. The old ritual "execute the full case manually before automating" is dead. Live investigation is a tool at your discretion, not a phase you owe — see Phase 2.
What ships with it
6 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.
- 10d ago First seen · 386 lines · 82 tokens per session scan A 14ed0a9a9f49
test-automation-implementation is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 9,641 once invoked, about $0.0004 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
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.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.