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 Netcracker/qubership-ai-packages --skill test-authoringgit clone --depth 1 https://github.com/Netcracker/qubership-ai-packagesWrote 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/netcracker/qubership-ai-packages/test-authoring)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/test-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/test-authoring/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/netcracker/qubership-ai-packages/test-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/test-authoring.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.00234 | $0.14718 |
| Opus 5.5 | $0.00094 | $0.05887 |
| Sonnet 5.5 | $0.00047 | $0.02944 |
| Haiku 4.5 | $0.00023 | $0.01472 |
Grade A, and why
test-authoring 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 — 794 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring a test
This skill governs what a test establishes, at which level, with which inputs, and how its failure reads. Wording,
tone, and the phrasing of a name or a message once its content is decided belong to the developer-style skill of the
language the repository writes in: english-developer-style unless the repository's instructions name another, such
as russian-developer-style or french-developer-style; load it too. The comment or docstring above a test belongs
to the doc-comment skill of its programming language (javadoc-authoring, godoc-authoring, pythondoc-authoring,
rustdoc-authoring, jsdoc-authoring). The commit message and the pull request description belong to
change-description-authoring.
Where the expected value is unknown and has to be learned by querying another system (a legacy service being ported, a
vendor binary without source, a reference stand that answers a parity or golden suite), which questions to send it is
blackbox-test-design's subject; load it too. This skill still governs each test that carries a question.
0. Which references to open
The rules below hold in every framework. What each framework prints, which of its assertions carry the values, where
the message goes, and how a case is named are in references/, one file per role a library plays in the test,
grouped by ecosystem. Before writing the first assertion, read the file for the project's test engine and the file
for its assertion library (a matcher library on JUnit adds the JUnit assertions file, as the rule on report forms
below says). Open the other roles' files where the change calls for them, and no other.
| Role | Decides | Files |
|---|---|---|
| Test engine | The container and the name in the report (§7), parameterized case names, random order (§8) | java/junit5.md (JUnit 5 and 6), java/junit4.md, python/pytest.md, go/testing.md, rust/libtest.md, javascript/jest.md, javascript/vitest.md, javascript/node-test.md |
| Assertion library | Which call prints the operands, the operand order, where the message goes, grouped assertions, error assertions (§7) | java/junit5-assertions.md, java/junit4-assert.md, java/assertj.md, java/truth.md, java/hamcrest.md, go/testify.md. pytest, Go testing, cargo test, Jest, Vitest, and node:test are both engine and assertions, and their engine file covers this role |
| Test doubles | How the shapes of §5 and §6 look in the library, what a verification failure prints | java/mockito.md |
| Property-based testing | The seed, the reproducer, the explicit example a counterexample becomes (§4) | java/jetcheck.md |
| Structural tests | The test on an open set of classes (§4) | java/archunit.md |
| Mutation | What the tool's verdicts mean (§1, §10) | mutation-tools.md, one table covering every ecosystem |
What ships with it
18 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.
- references/go/testify.md 2.6 KB
- references/go/testing.md 5.6 KB
- references/java/archunit.md 2.6 KB
- references/java/assertj.md 2.5 KB
- references/java/hamcrest.md 1.6 KB
- references/java/jetcheck.md 2.3 KB
- references/java/junit4-assert.md 2.6 KB
- references/java/junit4.md 4.0 KB
- references/java/junit5-assertions.md 2.7 KB
- references/java/junit5.md 3.9 KB
- references/java/mockito.md 3.5 KB
- references/java/truth.md 1.7 KB
- references/javascript/jest.md 4.0 KB
- references/javascript/node-test.md 4.1 KB
- references/javascript/vitest.md 3.9 KB
- references/mutation-tools.md 1.8 KB
- references/python/pytest.md 4.6 KB
- references/rust/libtest.md 4.6 KB
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 Changed · +4 lines 8fb33e4c3d49
- 12d ago Changed · +294 lines · +9 tokens per session 02fdd7e32edd
- 1mo ago First seen · 496 lines · 225 tokens per session scan A fad69497976c
test-authoring is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed today), licensed Apache-2.0. It adds 234 tokens to every session and 14,718 once invoked, about $0.0009 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-09-10.
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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.