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 nylo-core/claude-code --skill nylo-testinggit clone --depth 1 https://github.com/nylo-core/claude-codeWrote 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/nylo-core/claude-code/nylo-testing)<a href="https://agentmods.dev/skills/nylo-core/claude-code/nylo-testing"><img src="https://agentmods.dev/badge/skills/nylo-core/claude-code/nylo-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/nylo-core/claude-code/nylo-testing"><img src="https://agentmods.dev/badge/skills/nylo-core/claude-code/nylo-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.00049 | $0.02768 |
| Opus 5.5 | $0.00020 | $0.01107 |
| Sonnet 5.5 | $0.00010 | $0.00554 |
| Haiku 4.5 | $0.00005 | $0.00277 |
Grade A, and why
nylo-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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nylo Testing
Overview
Nylo v7 provides a Laravel-inspired testing framework built on top of Flutter's test library. It includes helpers for widget testing, API mocking, authentication simulation, time manipulation, factories with fake data, and a rich set of custom assertions. Tests live in the test/ directory and use nyTest, nyWidgetTest, and nyGroup as entry points.
When to Use
- Writing unit tests for models, services, or utility functions
- Writing widget tests for NyPage or NyState-based pages
- Mocking API responses for network-dependent tests
- Simulating authenticated or guest users in tests
- Testing time-sensitive logic with time travel helpers
- Generating fake data with factories and NyFaker
- Asserting routes, state updates, toast messages, or lock/loading states
- When NOT to use: for standard Flutter widget tests that do not involve Nylo's state, routing, or API layers, use Flutter's built-in test utilities directly
Quick Reference
| Task | Code |
|---|---|
| Initialize test file | NyTest.init() at top of test body |
| Unit test | nyTest('name', () async { ... }) |
| Widget test | nyWidgetTest('name', (tester) async { ... }) |
| Group tests | nyGroup('name', () { ... }) |
| Pump a NyPage | await tester.pumpNyWidget(child: MyPage()) |
| Pump and wait for init | await tester.pumpNyWidgetAndWaitForInit(child: MyPage()) |
| Mock API response | NyMockApi.respond('/users', {'id': 1}) |
| Simulate auth user | NyTest.actingAs<User>(User(name: "Test")) |
| Travel to a time | NyTest.travel(DateTime(2025, 6, 15)) |
| Create factory model | NyFactory.make<User>() |
| Fire state update | fireStateUpdate('HomePageState', data: {...}) |
| Debug test state | NyTest.dump() |
Test File Structure
import 'package:flutter_test/flutter_test.dart';
import 'package:nylo_framework/nylo_framework.dart';
void main() {
NyTest.init();
nySetUpAll(() async {
// Runs once before all tests
});
nySetUp(() async {
// Runs before each test
});
nyTearDown(() async {
// Runs after each test
});
nyTearDownAll(() async {
// Runs once after all tests
});
nyTest('my unit test', () async {
expect(1 + 1, equals(2));
});
nyWidgetTest('my widget test', (tester) async {
await tester.pumpNyWidget(child: MyPage());
expect(find.text('Hello'), findsOneWidget);
});
nyGroup('user tests', () {
nyTest('can create user', () async {
// ...
});
});
}
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 · 424 lines · 49 tokens per session scan A 926b5454c294
nylo-testing is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 2,768 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
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
flutter-testing
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or…
flutter-testing
Covers Flutter testing across all three layers: unit tests (business logic, ViewModels, repositories), widget tests (UI rendering, interactions, golden regression), and integration/E2E tests (full app flows, native OS interactions). Use this skill when writing any Flutter test, setting up mocking with mocktail or…
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).