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 OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill solid-impl-testinggit clone --depth 1 https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-ComposerWrote 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/openaec-foundation/openaec-workspace-composer/solid-impl-testing)<a href="https://agentmods.dev/skills/openaec-foundation/openaec-workspace-composer/solid-impl-testing"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-impl-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/openaec-foundation/openaec-workspace-composer/solid-impl-testing"><img src="https://agentmods.dev/badge/skills/openaec-foundation/openaec-workspace-composer/solid-impl-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.00103 | $0.02363 |
| Opus 5.5 | $0.00041 | $0.00945 |
| Sonnet 5.5 | $0.00021 | $0.00473 |
| Haiku 4.5 | $0.00010 | $0.00236 |
Grade A, and why
solid-impl-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.
How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solid-impl-testing
Quick Reference
Installation
npm install --save-dev @solidjs/testing-library @testing-library/jest-dom vitest
npm install --save-dev vite-plugin-solid
Key Dependencies
| Package | Role |
|---|---|
@solidjs/testing-library |
SolidJS-specific render, cleanup, renderHook, testEffect |
@testing-library/dom |
Re-exported: screen, fireEvent, waitFor, within, queries |
@testing-library/jest-dom |
DOM matchers (toBeInTheDocument, toHaveTextContent) |
vitest |
Test runner (recommended over Jest for SolidJS) |
vite-plugin-solid |
Compiles JSX/TSX for tests (v2.8.2+ handles test config automatically) |
Vitest Configuration
// vite.config.ts
import { defineConfig } from "vitest/config";
import solidPlugin from "vite-plugin-solid";
export default defineConfig({
plugins: [solidPlugin()],
resolve: {
conditions: ["development", "browser"],
},
test: {
environment: "jsdom",
globals: true,
setupFiles: ["./src/test-setup.ts"],
deps: {
optimizer: {
web: {
include: ["solid-js", "@solidjs/router"],
},
},
},
},
});
// src/test-setup.ts
import "@testing-library/jest-dom";
Critical Warnings
ALWAYS pass a function returning JSX to render() -- NEVER pass JSX directly. SolidJS render() requires () => <Component />, not <Component />. Passing JSX directly executes it outside the test's reactive owner and breaks cleanup.
ALWAYS call cleanup() in afterEach -- even though the library claims auto-cleanup, explicitly calling it prevents disposal errors across test suites. Omitting cleanup causes reactive owners to leak between tests.
NEVER use rerender() -- it does NOT exist in solid-testing-library. SolidJS does not re-render; it executes side effects from reactive state changes. Use signals to drive state changes in tests instead.
NEVER destructure props in test components -- this breaks reactivity tracking. Use props.value access patterns, same as production components.
What ships with it
3 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.
- 2mo ago First seen · 316 lines · 103 tokens per session scan A 184456da3ccc
solid-impl-testing is a skill published in the GitHub repository OpenAEC-Foundation/OpenAEC-Workspace-Composer (6 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 2,363 once invoked, about $0.0004 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
单元测试自动生成
A unit-test generator for core functions, edge cases, invalid inputs, and regression scenarios. Unit tests are small automated checks for individual pieces of code.
aios-prompt-compare
An internal testing workflow for comparing prompts and coding-agent skills on the same input. It compares a weak prompt, a reusable stronger prompt, and the result from a real skill, while preserving the original outputs.
aios-arch-health
Deterministic architecture-health governance for repositories. Use when a project needs complexity, duplication, dependency, test, coverage, mutation, QA, performance, database, concurrency, or failure-injection evidence; evidence provenance and artifact digests; protected specification, test, quality-profile, or QA…
Write tests
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
test-fixture-designer
Use when the user asks to design, create, simplify, repair, or review test fixtures, factories, builders, seeded datasets, temporary files, or test environment setup. Produce minimal, explicit, isolated data that makes tests readable, deterministic, and safe to clean up.
unit-test-engineer
Use when the user asks to create, improve, review, or repair unit tests for a function, module, component, or isolated behavior. Derive observable contracts from real code, keep tests deterministic and focused, and use the repository's existing test runner and helpers.