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 eea/eea.agent.skills --skill testinggit clone --depth 1 https://github.com/eea/eea.agent.skillsWrote 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/eea/eea.agent.skills/testing)<a href="https://agentmods.dev/skills/eea/eea.agent.skills/testing"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/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/eea/eea.agent.skills/testing"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/testing.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.00045 | $0.01530 |
| Opus 5.5 | $0.00018 | $0.00612 |
| Sonnet 5.5 | $0.00009 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Use this skill when a repository needs a test workflow developers and Jenkins run identically, or when coverage needs to go up for real rather than by gaming the number.
Primary goal
Two goals, in order:
- Parity — the same test commands run identically for the developer, the agent, and Jenkins. Mostly mechanical; see "Parity contract" below, which defers detail to
docker-expertandjenkins-pipelinerather than restating it. - Quality — coverage increases come from tests that exercise real behavior, not from tests written to move a number. This is the harder, ongoing part, and where this skill should keep growing.
When to use
Use this skill when you need to:
- close a real coverage gap (e.g. moving from 60% to 80%) with tests that exercise actual behavior, not just whichever lines are easiest to hit
- audit whether existing tests are meaningful or just inflate the coverage number
- define canonical test commands for a repository and confirm Jenkins and local testing run them identically
- avoid relying on Make as the only entrypoint for running tests
Parity contract
The commands Jenkins runs must be the same commands a developer can run locally with Docker. Jenkins must never hide the real commands inside Groovy only, and Make — if the repository uses it — must never be the only usable interface; a developer without Make must still be able to run the equivalent command.
For every Jenkins quality/test stage, be able to answer:
- what exact Docker command does Jenkins run?
- what exact Docker command should a developer run locally?
- are these the same command, or an obviously equivalent wrapper?
If the answer is no, fix that before touching test content — a coverage number from a stage you can't reproduce locally isn't one you can trust.
For the Dockerfile.test contract (what the image must contain, dependency-install rules, mixed-language guidance), see docker-expert/EEA-OVERRIDES.md's "Dockerfile.test for Jenkins Pipelines" — that's the canonical source, not restated here. For the Jenkinsfile phases that build, preflight, and generate around it, see jenkins-pipeline's Required workflow.
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 First seen · 111 lines · 45 tokens per session scan A 483c70c48d17
testing is a skill published in the GitHub repository eea/eea.agent.skills (5 stars, last pushed 20d ago), licensed MIT. It adds 45 tokens to every session and 1,530 once invoked, about $0.0002 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-31.
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.