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/adambien/airails/system-testsnpx skills add AdamBien/airails --skill system-testsgit clone --depth 1 https://github.com/AdamBien/airailsWrote 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/adambien/airails/system-tests)<a href="https://agentmods.dev/skills/adambien/airails/system-tests"><img src="https://agentmods.dev/badge/skills/adambien/airails/system-tests.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.00157 | $0.00540 |
| Opus 5 | $0.00078 | $0.00270 |
| Sonnet 5 | $0.00031 | $0.00108 |
| Haiku 4.5 | $0.00016 | $0.00054 |
Grade A, and why
system-tests 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.
What it actually says
System Tests
A system test exercises the running system from the outside through its public surface — HTTP, CLI, messaging, files. It observes what a consumer observes; nothing else.
Contract
- Black box — assert only through the public surface: no mocks, no internal classes, no database access unless the database is the public surface. Behavior not observable from outside is a unit or integration concern.
- Running system — tests target a started instance and never instantiate production classes. Starting and deploying is the stack skill's concern.
- Coordinates as configuration — base URL, broker address, working directory come from configuration (e.g. microprofile-server's
service_uriconfigKey), never hardcoded. The same suite runs unchanged against dev, CI, and a migration target. - Isolation — each test runs alone and in any order; seed-data assumptions are declared, not implied.
- Total reporting — every test appears in the result with a verdict; skipped is a verdict, not an omission.
Expectation Origins
Same test level, different oracle:
| Origin | Expected values come from | Skill |
|---|---|---|
| Specified | hand-written from known requirements | (default) |
| Spec-derived | EARS statements of a capability spec | ears-tests |
| Recorded | golden masters of the running legacy system | characterization-tests |
Composition
- This skill owns the contract above.
- The composed stack skill owns launch mechanics, module layout, and test syntax — microprofile-server:
-stMaven module, JUnit 5, rest client; java-cli-app: zunit; web frontends: web-system-tests (Playwright against the running site). - ears-tests and characterization-tests own their expectation origins and compose with both this skill and the stack skill.
What ships with it
1 file 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.
- 4d ago First seen · 33 lines · 157 tokens per session scan A 533f84317e43
system-tests is a skill published in the GitHub repository AdamBien/airails (48 stars, last pushed 14d ago), licensed MIT. It adds 157 tokens to every session and 540 once invoked, about $0.0008 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
security-regression-tests
Turning a confirmed and fixed finding into a permanent guard: proving the test fails without the fix, asserting the effect and not only the status code, seeding the two principals an authorization test needs, making a timing or out-of-band proof deterministic enough for CI, and keeping the test in a job that can…
zeus-test-gen
Generate AI-authored platform test flows (android.test.json, chrome.test.json, ios.test.json) from task.json and prd.json using generate-tests.sh. Can be triggered manually or automatically after zeus-plan. Supports --version flag and --platforms filter.
integration-testing
写集成/端到端测试时使用。测真实交互,稳定不脆弱。.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
qa
QA Specialist Agent for smoke testing production deployments. Runs Playwright-based smoke tests against live URLs to verify health, auth flows, protected routes, and core UI. Use when validating a deploy, checking if a production app is working, or when asked to run QA on a project.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.