Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nebius/nebius-physical-ainpx agentmods add skills/nebius/nebius-physical-ai/testing-conventionsWrote 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/nebius/nebius-physical-ai/testing-conventions)<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/testing-conventions"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/testing-conventions.svg" alt="Measured on agentmods" 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.00020 | $0.01974 |
| Opus 5 | $0.00010 | $0.00987 |
| Sonnet 5 | $0.00004 | $0.00395 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
testing-conventions 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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Conventions
Use the repository virtualenv. Never use bare python; use npa/.venv/bin/python.
Correct command from repo root:
npa/.venv/bin/python -m pytest npa/tests/ --ignore=npa/tests/e2e --timeout=120 -q
Correct command from inside npa/:
cd npa
.venv/bin/python -m pytest tests/ --ignore=tests/e2e --timeout=120 -q
Run it in parallel. The suite is xdist-safe (pytest-xdist is in the dev
extra); -n auto takes ~6 min down to ~2 min on 8 cores with an identical pass
count, which is the difference between running the whole suite each iteration and
only running a slice:
.venv/bin/python -m pytest tests/ -q -n auto
Use the serial form when a failure needs a readable, ordered traceback. CI still runs serially with coverage, so treat a parallel pass as the fast signal, not as a replacement for the gate.
Docs drift is a required gate and is slow to re-run blind. scripts/build_docs.sh
memoizes and prefetches its npa --help walk (~1 min, was ~5), but it still costs a
minute — so change CLI options first, then regenerate once, rather than checking
after each edit. Per-subcommand options do not change the generated pages; a new
top-level command adds docs/cli/<name>.md plus a README index line.
ruff is available in the venv:
npa/.venv/bin/python -m ruff check <files>
Existing Failures And Gates
- Known pre-existing failure:
tests/smoke/test_cosmos_serverless_smoke.pyhas 5 tests gated byNPA_COSMOS_SERVERLESS_SMOKE=1; they fail withUnable to list Nebius VPC networks for project project-smoke: unsupported. - E2E tests are gated by
NPA_INTEGRATION_E2E=1and excluded from standard runs with--ignore=npa/tests/e2e. - Pipeline E2E tests use the
e2e_pipelinepytest marker. - Live Nebius Token Factory tests use the
token_factory_e2emarker (innpa/tests/e2e/test_token_factory_e2e.py). They self-skip without a realNEBIUS_TOKEN_FACTORY_KEY; the marker is in conftest_LIVE_MARKERSso the key is not scrubbed. Run withNEBIUS_TOKEN_FACTORY_KEY=... pytest npa/tests/e2e/test_token_factory_e2e.py.
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.
- today Changed · +8 lines 00cc8500badb
- 8d ago First seen · 136 lines · 20 tokens per session scan A b39296cd5660
testing-conventions is a skill published in the GitHub repository nebius/nebius-physical-ai (27 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 1,974 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-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.