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 AdamBien/airails --skill continuous-testinggit 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/continuous-testing)<a href="https://agentmods.dev/skills/adambien/airails/continuous-testing"><img src="https://agentmods.dev/badge/skills/adambien/airails/continuous-testing/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/adambien/airails/continuous-testing"><img src="https://agentmods.dev/badge/skills/adambien/airails/continuous-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00446 |
| Opus 5.5 | $0.00034 | $0.00178 |
| Sonnet 5.5 | $0.00017 | $0.00089 |
| Haiku 4.5 | $0.00008 | $0.00045 |
Grade A, and why
continuous-testing 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 1mo 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
Continuous test-driven development loop using $ARGUMENTS. Apply all rules from /microprofile-server, plus the verification loop below.
Server Lifecycle
- start Quarkus in dev mode (
mvn quarkus:dev) once at the beginning of the session - keep the server running across changes — Quarkus dev mode handles live reload automatically
- only restart the server on major errors (e.g., server crash, port conflict, unrecoverable startup failure)
- do not stop and restart the server between changes
Verification Loop
After every code change, execute the following steps in order:
- Build & Unit Tests — run
mvn testin the service module to compile and execute unit tests - Integration Tests — run
mvn verifyin the service module to execute integration tests (failsafe plugin) - System Tests — before running, verify that the
-stmodule'spom.xmlincludes themaven-failsafe-pluginconfiguration. Then runmvn verifyin the-stmodule against the running server (already running in dev mode)
Rules
- do not skip any step — every change triggers the full loop
- if unit tests fail, stop and fix before proceeding to integration tests
- if integration tests fail, stop and fix before proceeding to system tests
- if system tests fail, stop and fix before continuing with the next change
- report the outcome of each step before proceeding to the next
- treat compilation errors as a failed step — fix before continuing
- keep the loop running until all steps pass or the user intervenes
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.
- 1mo ago Changed · +1 lines a9a83857d116
- 1mo ago First seen · 32 lines · 84 tokens per session scan A 773e78bd1c94
continuous-testing is a skill published in the GitHub repository AdamBien/airails (58 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 446 once invoked, about $0.0003 per session on Opus 5.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
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.
langchain4j-testing-strategies
Provides unit test, integration test, and mock AI patterns for LangChain4j applications. Creates mock LLM responses, tests retrieval chains, validates RAG workflows, and implements Testcontainers-based integration tests for Java AI services. Use when unit testing AI services, integration testing LangChain4j…
unit-test-parameterized
Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value…
unit-test-mapper-converter
Provides patterns for unit testing mappers, converters, and bean mappings. Validates entity-to-DTO and model transformation logic in isolation. Generates executable mapping tests with MapStruct and custom converter test coverage. Use when writing mapping tests, converter tests, entity mapping tests, or ensuring…
unit-test-scheduled-async
Provides patterns for unit testing Spring @Scheduled and @Async methods using JUnit 5, CompletableFuture, Awaitility, and Mockito. Covers mocking task execution and timing, verifying execution counts, testing cron expressions, validating retry behavior, and simulating thread pool behavior. Use when testing background…
unit-test-service-layer
Provides patterns for unit testing service layer with Mockito. Creates isolated tests that mock repository calls, verify method invocations, test exception scenarios, and stub external API responses. Use when testing service behaviors and business logic without database or external services.