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/nguyenthanhtat/screen1-claudenpx agentmods add skills/nguyenthanhtat/screen1-claude/test-fullyWrote 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/nguyenthanhtat/screen1-claude/test-fully)<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/test-fully"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/test-fully/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/nguyenthanhtat/screen1-claude/test-fully"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/test-fully.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.00000 | $0.04810 |
| Opus 5 | $0.00000 | $0.02405 |
| Sonnet 5 | $0.00000 | $0.00962 |
| Haiku 4.5 | $0.00000 | $0.00481 |
Grade A, and why
test-fully 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 9d 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 — 810 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Fully - Comprehensive Testing Skill
Version
- Version: 1.0.0
- Last Updated: 2025-02-10
- Compatibility: All major testing frameworks
Purpose
Generate comprehensive test suites covering unit, integration, E2E, and performance testing for any codebase. Automatically detects testing frameworks and follows language-specific best practices.
How to Use This Skill
Quick Usage
# Test specific file
/test-fully src/utils/validator.js
# Test with focus on specific type
/test-fully --focus unit
/test-fully --focus integration
/test-fully --focus e2e
/test-fully --focus performance
# Test entire module
/test-fully src/features/auth/
# Update existing tests
/test-fully update tests for payment.js
Testing Strategy
When this skill is invoked, I will:
1. Code Analysis Phase
- Read and understand the codebase structure
- Identify all functions, methods, and components
- Map dependencies and integration points
- Detect existing patterns and conventions
2. Framework Detection Phase
Automatically identify the testing framework in use:
JavaScript/TypeScript:
- Jest (check for jest.config.js, package.json scripts)
- Vitest (check for vitest.config.ts)
- Mocha + Chai (check for .mocharc.json)
- Jasmine (check for jasmine.json)
Python:
- pytest (check for pytest.ini, conftest.py)
- unittest (check for test_*.py pattern)
- nose2 (check for nose2.cfg)
Java:
- JUnit 5 (check for @Test annotations, pom.xml)
- JUnit 4 (check for older @Test imports)
- TestNG (check for testng.xml)
Other Languages:
- Go:
testingpackage - Ruby: RSpec or Minitest
- C#: xUnit, NUnit, or MSTest
- PHP: PHPUnit
- Rust: Built-in test framework
E2E Frameworks:
- Playwright
- Cypress
- Selenium
- Puppeteer
3. Test Generation Phase
Create tests covering:
A. Unit Tests
Focus: Individual functions/methods in isolation
Coverage Areas:
- ✅ Happy path (valid inputs, expected outputs)
- ✅ Edge cases (empty strings, null, undefined, zero, negative numbers)
- ✅ Boundary conditions (min/max values, limits)
- ✅ Type validation (wrong types, type coercion)
- ✅ Error handling (exceptions, error messages)
- ✅ State management (before/after state changes)
- ✅ Side effects (external calls, mutations)
What ships with it
5 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.
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.
- 9d ago First seen · 810 lines · 0 tokens per session scan A d6928fd59184
test-fully is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,810 tokens. 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
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.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
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.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…