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 DDS-Solutions/AI-TadPole-OS --skill testing-patternsgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/testing-patterns)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/testing-patterns"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/testing-patterns/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/dds-solutions/ai-tadpole-os/testing-patterns"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01030 |
| Opus 5.5 | $0.00013 | $0.00412 |
| Sonnet 5.5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
testing-patterns 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / testing-patterns
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Flaky non-deterministic tests, coupled mock state, or assertions without behavioral verification.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Testing Patterns & Verification Principles
Standard: Arrange-Act-Assert (AAA). Fast, deterministic, isolated unit tests.
Workflow Bindings: Integrated directly into/testand/adversary.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign testing principles below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/mocking_and_fixture_patterns.md |
Test double taxonomy (Mocks vs Spies vs Fakes), async Rust & Vitest fixtures | Writing unit and integration tests |
scripts/test_runner.py |
Automated multi-ecosystem test executor (Vitest, Cargo, Pytest) with built-in self-tests | Running test suites across workspace boundaries |
📐 1. The AAA Pattern (Arrange-Act-Assert)
it('calculates USD token burn correctly', () => {
// 1. Arrange: Prepare mock fixtures and state
const tokenTracker = new TokenTracker({ ratePerThousand: 0.002 });
// 2. Act: Execute function under test
const cost = tokenTracker.calculateCost(5000);
// 3. Assert: Verify outcome matches specification
expect(cost).toBe(0.01);
});
⚡ 2. Unit vs Integration Boundaries
| Test Layer | Target & Scope | Execution Speed Target |
|---|---|---|
| Unit | Pure functions, domain calculations, StateFlow reducers | Blazing ($<50$ms per test) |
| Integration | Axum router handlers, SQLite queries, WebSocket broadcasts | Fast (100–500ms) |
| E2E / Swarm | Multi-agent swarms & end-to-end browser flows | Bounded (1–5s) |
What ships with it
2 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 Changed · +27 lines · +16 tokens per session 466b312abdaa
- 1mo ago First seen · 67 lines · 16 tokens per session scan A 790fddfe8359
testing-patterns is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,030 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-09-03.
Other skills, from other repositories
authoring-data-quality-checks
Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views, and HogQL catalog metrics: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Metrics support custom SQL checks only. Use when asked to test a…
authoring-benchmarks
Design, implement, run, debug, and interpret browser performance benchmarks for Elements components and utilities. Use whenever the user asks to benchmark or performance-test runtime code, create or update a .test.bench.ts file, compare benchmark results, investigate a browser performance regression, understand Vitest…
test-building-blocks
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…
component-tester
Run Vitest tests for a specific component with coverage. Use when making changes to React components to ensure tests pass and coverage is maintained.
unit-test
Testing patterns for the Python/FastAPI + React/TypeScript stack. Covers pytest configuration, conftest fixtures, database safety guards, external API mocking, async tests, Celery eager mode, and Vitest for frontend.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.