Borrowing it
Nothing to install: this file belongs to susomejias/rembric. 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/susomejias/rembric/main/.agents/skills/testing/SKILL.mdgit clone --depth 1 https://github.com/susomejias/rembricWrote 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/susomejias/rembric/testing)<a href="https://agentmods.dev/skills/susomejias/rembric/testing"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/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/susomejias/rembric/testing"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/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.00675 |
| Opus 5.5 | $0.00020 | $0.00270 |
| Sonnet 5.5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Design tests that increase confidence, survive refactors, and reflect real usage.
Reference Map
- Read references/strategy.md when deciding what to test, how much to test, or how to prioritize coverage.
- Read references/fundamentals.md when you need the core mental model for assertions, frameworks, isolation, and useful failures.
- Read references/interaction-testing.md when testing user-visible behavior, flows, or observable system interactions.
- Read references/quality-gates.md when deciding how static checks, automated tests, manual checks, and delivery gates should work together.
- Read references/mocking.md when dealing with stubs, spies, mocks, randomness, or flaky external boundaries.
- Read references/glossary.md when the user asks about testing terminology.
Defaults
- Test behavior through public interfaces.
- Follow a testing trophy bias: lean on static checks and integration tests, with fewer unit and end-to-end tests.
- Prefer a few high-value integration tests over many shallow micro-tests.
- Mock only real boundaries: network, time, randomness, payments, third-party APIs.
- Choose assertions a user, caller, or downstream system would care about.
- Keep tests deterministic, small, and readable.
Workflow
- Identify the highest-risk behavior or workflow.
- Pick the cheapest test level that can prove it: static, unit, integration, or end-to-end.
- Arrange realistic inputs, state, and environment.
- Act through the public API, visible surface, or command boundary.
- Assert observable outcomes, not internal steps.
- Keep failures specific and setup cleanup reliable.
- Remove setup, mocks, and assertions that do not increase confidence.
Test Level Guide
- Unit: pure logic, parsing, formatting, branching, edge cases.
- Integration: component or service workflows, validation, state changes, error handling.
- End-to-end: a few critical user journeys or irreversible flows.
What ships with it
6 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.
- 1mo ago First seen · 62 lines · 49 tokens per session scan A a71e17c75cc6
testing is a skill published in the GitHub repository susomejias/rembric (14 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 675 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-30.
Other skills, from other repositories
indie-product
A documented workflow for building an independent product, from validating a user problem through defining scope, development, testing, release, and feedback. It records requirements, decisions, defects, test results, and follow-up work.
mini-app
A structured workflow and document library for building and releasing a small app, covering user needs, page flows, development, platform review, and launch checks.
mobile-app
A documented workflow for developing and releasing a mobile application. It covers requirements, interaction design, client and service integration, device testing, permissions, store submission, and post-release feedback.
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
release-preflight
Run the release hard-precondition gate before any tag/OTA — apc release preflight runs the real tier gate (run.ts), version alignment, and prisma regen check, all read-only. green(0) releasable · staged(3) fixable preconditions · blocked(1) tier red/envblocked. No push, no write.
nestjs
Use when building or structuring a NestJS backend — feature modules, providers and DI wiring, provider scopes and request-lifecycle order, where to bind guards/pipes/interceptors/filters, and testing with Test.createTestingModule. NOT a bare Express/Fastify service with no DI (that is nodejs), NOT framework-agnostic…