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 niels-emmer/myace --skill test-automationgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/test-automation)<a href="https://agentmods.dev/skills/niels-emmer/myace/test-automation"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/test-automation/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/niels-emmer/myace/test-automation"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/test-automation.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.00468 |
| Opus 5 | $0.00015 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
Test Automation 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 7d 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.
What it actually says
Purpose
A test suite only earns its keep if it runs fast and reliably — in CI, on every change, without a human babysitting flaky failures. This skill is a checklist for keeping automated tests deterministic, isolated, and cheap enough to run often.
When to use it
When writing or reviewing automated tests, setting up CI test runs, or debugging a flaky test.
Checklist
- Isolate tests from each other. No shared mutable state, no ordering dependencies, no test that depends on another test having run first. Each test sets up what it needs and cleans up after itself.
- Mock at the boundary, not the behavior. Mock external dependencies (network, time, filesystem, databases) at the interface, and keep the mock's behavior realistic — a mock that only returns the success response isn't testing the failure path at all.
- Control time and randomness. Freeze clocks, seed random generators, and avoid wall-clock timing assertions. A test that passes only when the machine is fast enough is a flaky test.
- Keep the suite fast. Fast tests get run more often. If a test is slow, ask whether it's at the right level before accepting the cost.
- Flakiness is a defect. A flaky test erodes trust in every result. Fix the root cause (timing, ordering, shared state) rather than retrying, skipping, or deleting the test.
- CI runs the real suite. The CI gate runs the same tests a developer runs locally — no "CI-only" suite that diverges from what's verified on a machine.
Expected output
A suite that runs deterministically in CI on every change: isolated tests, realistic mocks, controlled time/randomness, and no flaky failures — fast enough that running it is the default, not a chore.
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.
- 7d ago First seen · 28 lines · 29 tokens per session scan A 28bacff3fb39
Test Automation is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 468 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-09-03.
Other skills, from other repositories
keel
Measure whether a codebase's verification actually touches the world, or whether it is checking itself. Keel gathers the verification edges it can read in a target (GitHub Actions, CircleCI, GitLab CI, Travis, package scripts, Makefile, Rakefile, pyproject and a dozen tool configs) — and reports the surfaces it…
fitness-functions
Define objective, measurable tests for architectural characteristics and wire them into CI as automated, continuous architecture governance.
ci-pipeline-design
Build a CI pipeline that's fast, reliable, and actually catches regressions. Invoke when setting up or auditing build/test/deploy automation.
deploy
Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.