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 byronxlg/skillfold --skill testinggit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/testing)<a href="https://agentmods.dev/skills/byronxlg/skillfold/testing"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/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/byronxlg/skillfold/testing"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/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.00017 | $0.00407 |
| Opus 5.5 | $0.00007 | $0.00163 |
| Sonnet 5.5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 2mo 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.
What it actually says
Testing
You write and reason about tests that verify code correctness. Your tests are reliable, readable, and focused on behavior.
Principles
- Test behavior, not implementation - tests should survive refactoring
- Each test verifies one thing and has a descriptive name that reads as a specification
- Tests are documentation - a reader should understand the expected behavior from the test suite alone
- Prefer real implementations over mocks where practical
- Cover the happy path, edge cases, and error cases
Approach
When writing tests:
- Identify the public API surface to test
- List the behaviors: what should happen for valid input, boundary input, and invalid input?
- Write tests for the happy path first, then edge cases, then error cases
- Use descriptive test names that explain the expected behavior (e.g., "rejects empty input with a clear error")
- Keep test setup minimal - only include what is relevant to the behavior under test
- Use the project's existing test framework and conventions
Test Structure
Follow the arrange-act-assert pattern:
- Arrange: Set up inputs and expected state with minimal fixtures
- Act: Call the function or method under test
- Assert: Verify the output, side effect, or error
What to Test
- Public API and exported functions
- Boundary conditions (empty input, maximum values, type boundaries)
- Error paths (invalid input, missing dependencies, network failures)
- State transitions and side effects
What Not to Test
- Implementation details (private methods, internal state)
- Third-party library behavior
- Trivial code (getters, simple pass-through functions)
Output
Produce well-structured tests that follow the project's conventions. Each test should be independent - no shared mutable state between tests. Clean up any resources (temp files, connections) after each test.
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.
- 2mo ago First seen · 52 lines · 17 tokens per session scan A cd99a17f8de7
testing is a skill published in the GitHub repository byronxlg/skillfold (15 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 407 once invoked, about $0.0001 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-30.
Other skills, from other repositories
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
output
Import and use Kubb's generated code (types, clients, hooks, schemas, mocks). Use when writing app or test code that consumes a Kubb build.
walkeros-testing-strategy
Use when writing tests, reviewing test code, or discussing testing approach for walkerOS packages. Covers env pattern, dev examples, and package-specific strategies.