Borrowing it
Nothing to install: this file belongs to PedroMosquera/squadai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PedroMosquera/squadai/main/.agents/skills/testing/SKILL.mdgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/testing)<a href="https://agentmods.dev/skills/pedromosquera/squadai/testing"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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/pedromosquera/squadai/testing"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/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.00009 | $0.00476 |
| Opus 5.5 | $0.00004 | $0.00190 |
| Sonnet 5.5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
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 14d 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 Skill
Write tests for the specified code following a structured protocol. Produce thorough, maintainable tests that cover the important behavior.
Steps
-
Identify what to test: Analyze the code to determine test targets.
- Public API functions and methods
- Edge cases: empty inputs, nil/null values, boundary conditions
- Error paths: invalid input, missing dependencies, timeout conditions
- State transitions: before/after side effects
-
Choose test structure: Select the appropriate pattern.
- Table-driven tests: When testing the same function with multiple inputs.
- Arrange-Act-Assert (AAA): For single-scenario tests.
- Given-When-Then: For behavior-focused tests.
-
Name tests descriptively: Test names should explain the scenario.
- Format:
TestFunctionName_Scenario_ExpectedResult - Example:
TestValidate_EmptyInput_ReturnsError - Failed test names should make the failure obvious without reading the test body.
- Format:
-
Set up test fixtures: Prepare the test environment.
- Use temp directories for filesystem tests.
- Create minimal fixtures: only what the test needs.
- Clean up after tests (use deferred cleanup or framework helpers).
-
Write assertions: Verify behavior clearly.
- Assert on specific values, not just "no error."
- Check both positive cases (correct output) and negative cases (expected errors).
- Verify side effects (file created, state changed) when relevant.
-
Mock boundaries, not internals: Keep tests focused.
- Mock external dependencies: HTTP, databases, filesystems, clocks.
- Do not mock internal functions or private methods.
- Use interfaces at boundaries to enable test substitution.
-
Check coverage gaps: Review what is not yet tested.
- Concurrent access (if applicable).
- Large inputs or performance-sensitive paths.
- Integration between components (consider integration tests).
Output Format
Produce test code that:
- Follows the project's existing test conventions.
- Includes a brief comment explaining each test's purpose.
- Groups related tests together.
- Is runnable without modification.
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.
- 14d ago Changed · -5 lines · +6 tokens per session fe40350e0e79
- 15d ago Changed · +5 lines · -6 tokens per session 98dbb9744f8a
- 1mo ago First seen · 55 lines · 9 tokens per session scan A 164604472177
testing is a skill published in the GitHub repository PedroMosquera/squadai (10 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 476 once invoked, about $0.0000 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
update-package-skill
Updates an existing package Skill for a new release of its npm or local package by testing only what changed since the version the Skill names. Use when a maintainer asks to refresh a package Skill after a release, or when a SKILL.md names an older tested version than the package.
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…
senior-manual-qa
Execute senior-level manual QA for TypeScript libraries and CLI tools using risk-based planning, strict evidence collection, and reproducible defect reporting. Use when the user asks for full test plans, edge-case validation, release-readiness checks, or complete manual QA passes.
post-feature-qa
Apply after EVERY feature implementation, story completion, or task finish. Act as a senior QA engineer: make sure all edge cases are covered and implementation fully aligns with the story/spec. Use whenever you complete a story, ship a feature, or before marking a task done or opening a PR. Do not skip this — run the…