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/getlytos/lytos-clinpx agentmods add skills/getlytos/lytos-cli/testingWrote 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/getlytos/lytos-cli/testing)<a href="https://agentmods.dev/skills/getlytos/lytos-cli/testing"><img src="https://agentmods.dev/badge/skills/getlytos/lytos-cli/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/getlytos/lytos-cli/testing"><img src="https://agentmods.dev/badge/skills/getlytos/lytos-cli/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.00059 | $0.03111 |
| Opus 5.5 | $0.00024 | $0.01244 |
| Sonnet 5.5 | $0.00012 | $0.00622 |
| Haiku 4.5 | $0.00006 | $0.00311 |
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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill — Testing
This skill defines how to write tests on a project using Lytos. It covers unit tests and end-to-end tests. An agent loaded with this skill knows what to test, how to structure tests, and what coverage criteria to meet.
When to invoke this skill
- After writing a new feature
- After a fix — the test must prove the bug won't come back
- During a refactoring — existing tests must continue to pass
- During a quality audit — check overall coverage
Testing strategy
Follow the Testing Trophy model (Kent C. Dodds): the highest return on investment comes from integration tests, not unit tests.
╱╲ E2E — few, critical journeys only
╱ ╲
╱────╲
╱ ╲ Integration — the bulk of your tests
╱ ╲
╱──────────╲
╱ ╲ Unit — fast, focused, isolated logic
╱──────────────╲
╱________________╲ Static analysis — linting, type checking, formatting
| Layer | Volume | What it catches |
|---|---|---|
| Static analysis | Runs on every save/commit | Typos, type errors, style drift |
| Unit tests | Many, fast | Logic errors in pure functions |
| Integration tests | Most of your tests | Broken contracts between modules, DB queries, API routes |
| E2E tests | Few, slow | Critical user journeys broken across the full stack |
Write more integration tests than unit tests. Reserve E2E for the journeys where a failure means lost revenue or data.
Unit tests
Principles
- A unit test tests one single thing
- It is independent — does not depend on execution order or another test
- It is fast — no network calls, no database (use mocks)
- It is deterministic — the same input always gives the same result
Test file structure
tests/
├── unit/
│ ├── [module]/
│ │ └── [module].test.* <- depends on the project language
│ └── ...
└── e2e/
├── [feature].spec.* <- end-to-end tests
└── ...
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 · 416 lines · 59 tokens per session scan A 7271b7dcb4ac
testing is a skill published in the GitHub repository getlytos/lytos-cli (2 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 3,111 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.